Aryan Mishra
feat: initial commit - Multilingual ABSA project setup with 6 phases, 36 requirements
a6b96c2
|
Raw
History Blame Contribute Delete
2.3 kB
---
description: CRUD for phases in ROADMAP.md β€” add, insert, remove, or edit phases
argument-hint: "[--insert | --remove | --edit] <phase-name-or-number>"
tools:
read: true
write: true
bash: true
glob: true
---
<objective>
Manage phases in ROADMAP.md with a single consolidated command.
Mode routing:
- **default** (no flag): Add a new integer phase to the end of the current milestone β†’ add-phase workflow
- **--insert**: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases β†’ insert-phase workflow
- **--remove**: Remove a future phase and renumber subsequent phases β†’ remove-phase workflow
- **--edit**: Edit any field of an existing phase in place β†’ edit-phase workflow
</objective>
<routing>
| Flag | Action | Workflow |
|------|--------|----------|
| (none) | Add new integer phase at end of milestone | add-phase |
| --insert | Insert decimal phase (e.g., 72.1) after specified phase | insert-phase |
| --remove | Remove future phase, renumber subsequent | remove-phase |
| --edit | Edit fields of existing phase in place | edit-phase |
</routing>
<execution_context>
@/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/workflows/add-phase.md
@/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/workflows/insert-phase.md
@/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/workflows/remove-phase.md
@/Users/theogengineer/Projects/Multilingual-Absa/.opencode/gsd-core/workflows/edit-phase.md
</execution_context>
<context>
Arguments: $ARGUMENTS
Parse the first token of $ARGUMENTS:
- If it is `--insert`: strip the flag, pass remainder (format: <after-phase-number> <description>) to insert-phase workflow
- If it is `--remove`: strip the flag, pass remainder (phase number) to remove-phase workflow
- If it is `--edit`: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow
- Otherwise: pass all of $ARGUMENTS (phase description) to add-phase workflow
Roadmap and state are resolved in-workflow via `init phase-op` and targeted reads.
</context>
<process>
1. Parse the leading flag (if any) from $ARGUMENTS.
2. Load and execute the appropriate workflow end-to-end based on the routing table above.
3. Preserve all validation gates from the target workflow.
</process>