diff options
Diffstat (limited to 'makima/src/daemon/skills/directive.md')
| -rw-r--r-- | makima/src/daemon/skills/directive.md | 27 |
1 files changed, 26 insertions, 1 deletions
diff --git a/makima/src/daemon/skills/directive.md b/makima/src/daemon/skills/directive.md index 02de836..dc1bce2 100644 --- a/makima/src/daemon/skills/directive.md +++ b/makima/src/daemon/skills/directive.md @@ -92,7 +92,7 @@ Options: - `--choices "opt1,opt2,opt3"` - Provide choices for the user to select from - `--context "<context>"` - Additional context to help the user understand the question - `--timeout <seconds>` - Wait timeout (default: 3600 = 1 hour) -- `--phaseguard` - Block indefinitely until the user responds (no timeout). Recommended for critical decisions during planning. +- `--phaseguard` - Wait indefinitely until the user responds (no timeout). The CLI automatically reconnects via polling every ~5 minutes to avoid HTTP timeout limits. Recommended for critical decisions during planning. - `--multi-select` - Allow the user to select multiple choices - `--non-blocking` - Return immediately without waiting for a response - `--question-type <general|phase_confirmation|contract_complete>` - Question type @@ -108,6 +108,31 @@ Options: makima directive ask "Should we use REST or GraphQL for the new API?" --choices "REST,GraphQL" --context "The existing codebase uses REST but the frontend team prefers GraphQL" --phaseguard ``` +### Create an Order (Future Work) +```bash +makima directive create-order --title "Order title" --order-type spike +``` +Creates an order for future work that is automatically linked to the current directive. Only `spike` and `chore` order types are allowed. + +Options: +- `--title "<title>"` - (Required) Title of the order +- `--description "<description>"` - Optional description of the work +- `--priority <critical|high|medium|low|none>` - Priority level (default: medium) +- `--order-type <spike|chore>` - Type of work (default: spike). Only spike and chore are allowed. +- `--labels "label1,label2"` - Optional comma-separated labels + +**When to use:** +- When you discover work that is out of scope for the current directive step but should be tracked +- When a spike reveals follow-up tasks that need to be done later +- When you identify technical debt or maintenance work during implementation +- When a chore (e.g., dependency update, config change) is needed but not part of the current goal + +**Example:** +```bash +makima directive create-order --title "Investigate flaky test in auth module" --order-type spike --priority high --description "The auth module tests intermittently fail on CI. Needs investigation." --labels "testing,auth" +makima directive create-order --title "Update deprecated serde API usage" --order-type chore --priority low --labels "tech-debt" +``` + ## Memory Commands Directives have an optional key-value memory system that persists across steps and planning cycles. Use memory to share context, decisions, and learned information between steps — so downstream tasks don't need to re-discover what earlier steps already figured out. |