Use when managing planning phase: start planning, track progress, manage requirements/modules, or approve plans. Trigger with /start-planning or /planning-status commands.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Use when managing planning phase: start planning, track progress, manage requirements/modules, or approve plans. Trigger with /start-planning or /planning-status commands.
version
1.0.0
license
Apache-2.0
compatibility
Requires Python 3.8+, PyYAML, GitHub CLI for issue creation. Cross-platform compatible. Requires AI Maestro installed.
metadata
{"author":"Emasoft"}
user-invocable
false
context
fork
workflow-instruction
Step 6
procedure
proc-route-requirements
Planning Commands Skill
Overview
This skill documents all planning phase commands for the Architect Agent plugin. The planning phase is the first stage of the Two-Phase workflow where requirements are gathered, modules are defined, and the implementation plan is created before any code is written.
Prerequisites
Python 3.8+ with PyYAML installed
GitHub CLI for issue creation
Write access to .claude/ directory for state files
Understanding of Two-Phase workflow
Instructions
Use this skill when you need to:
Start a new project with formal requirements gathering
Track planning progress and requirements completion
Add, modify, or remove requirements and modules during planning
Approve a plan and transition to the orchestration phase
Typical workflow:
Start planning with /start-planning "goal"
Add requirements and modules with /add-requirement
Verify state file created at .claude/orchestrator-plan-phase.local.md
Add requirement sections as needed: /add-requirement requirement "Name"
Add modules with criteria: /add-requirement module "name" --criteria "..." --priority high
Create USER_REQUIREMENTS.md manually
Track progress: /planning-status
Mark requirement sections complete: /modify-requirement requirement "Name" --status complete
Verify all prerequisites met:
USER_REQUIREMENTS.md exists
All requirement sections marked complete
All modules have acceptance criteria
At least one module defined
Verify plan: /planning-status --verbose
Approve plan: /approve-plan
Verify GitHub Issues created for each module
Begin orchestration: /start-orchestration
Output
Each planning command produces structured output to the terminal showing the operation result and updated state. The /planning-status command displays a formatted table with phase status, requirements progress, and module list. The /approve-plan command outputs a transition summary including created GitHub Issue URLs. For detailed output format examples, see extended-examples-and-resources.md.
Commands Overview
Command
Purpose
Section
/start-planning
Enter Plan Phase Mode
1.0
/planning-status
View requirements progress
2.0
/add-requirement
Add requirement or module
3.0
/modify-requirement
Change requirement specs
4.0
/remove-requirement
Remove pending requirement
5.0
/approve-plan
Transition to Orchestration
6.0
1.0 When Starting a New Project
Use /start-planning to enter Plan Phase Mode and begin requirements gathering.
Command:
/start-planning "Goal description here"
What happens:
Creates state file at .claude/orchestrator-plan-phase.local.md
Locks the user goal (cannot change without approval)
