CLICommands
paddi request
Review and advance the requests analyzed from your captures.
Review and advance the requests analyzed from your captures.
paddi request list
List the requests in the current project, sorted by RIGE score (Reach × Impact × Goal Alignment ÷ Effort), highest first.
ID NAME TYPE STATUS SCORE
req_001 Export is hard to find feature scored 8.4paddi request view <request-id>
Show the request in full: each RIGE factor, the description, the analysis, how many captures it links to, its solution paths (with their options and current selections), and the generated spec if there is one.
Export is hard to find (req_001)
Type: feature Status: scored Score: 8.4
RIGE: reach 0.8 x impact 0.9 x goal 0.75 / effort 0.3
Description:
...
Solution paths:
1. Should the old export entry point stay? (sp_01)
Context: ...
- Keep it and add a shortcut — low risk, small build
- Remove it entirely — needs a migration guide
> selected: Keep it and add a shortcutpaddi request regenerate <request-id>
| Flag | Description |
|---|---|
--expectation, -e <text> | Steer the regenerated solution paths in a direction (optional) |
paddi request regenerate req_001 -e "prefer low-risk, incrementally shippable options"paddi request draft <request-id>
| Flag | Description |
|---|---|
--file, -f <path> | Required. JSON file holding the answers; pass - to read stdin |
Submitting answers triggers spec generation. The JSON can be a bare array or wrapped in {"answers": [...]}; each answer maps to one solution path:
[
{
"solution_path_id": "sp_01",
"selections": [{ "label": "Keep it and add a shortcut", "custom": false }]
}
]selections[].custom marks whether the selection is a custom answer the user typed rather than one of the offered options.
paddi request draft req_001 -f answers.json