メニュー
Use when managing planning phase: start planning, track progress, manage requirements/modules, or approve plans. Trigger with /start-planning or /planning-status commands.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/tomevault-io/skills-registry --skill eaa-requirements-analysisコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
SOC 職業分類に基づく
SKILL.md を表示中
| name | eaa-requirements-analysis |
| description | 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 |
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.
.claude/ directory for state filesUse this skill when you need to:
Typical workflow:
/start-planning "goal"/add-requirement/planning-status/modify-requirement/approve-planCopy this checklist and track your progress:
/start-planning "goal description".claude/orchestrator-plan-phase.local.md/add-requirement requirement "Name"/add-requirement module "name" --criteria "..." --priority high/planning-status/modify-requirement requirement "Name" --status complete/planning-status --verbose/approve-plan/start-orchestrationEach 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.
| 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 |
Use /start-planning to enter Plan Phase Mode and begin requirements gathering.
Command:
/start-planning "Goal description here"
What happens:
.claude/orchestrator-plan-phase.local.mdFor complete procedure details, see start-planning-procedure.md:
Use /planning-status to view the current state of Plan Phase.
Command:
/planning-status
/planning-status --verbose
Output shows:
Example output:
+------------------------------------------------------------------+
| PLAN PHASE STATUS |
+------------------------------------------------------------------+
| Plan ID: plan-20260109-143022 |
| Status: drafting |
| Goal: Build user authentication with OAuth2 |
+------------------------------------------------------------------+
| REQUIREMENTS PROGRESS |
+------------------------------------------------------------------+
| [x] Functional Requirements - complete |
| [>] Non-Functional Requirements - in-progress |
| [ ] Architecture Design - pending |
+------------------------------------------------------------------+
Use /add-requirement to add new requirement sections or modules to the plan.
Adding a requirement section:
/add-requirement requirement "Security Requirements"
Adding a module:
/add-requirement module "auth-core" --criteria "Support JWT tokens" --priority high
For complete details, see requirement-management.md:
Use /modify-requirement to change existing requirement sections or modules.
Modifying a requirement section:
/modify-requirement requirement "Functional Requirements" --status complete
Modifying a module:
/modify-requirement module auth-core --criteria "Support JWT and OAuth2" --priority critical
Modifiable fields:
| Field | Requirements | Modules |
|---|---|---|
| --name | Yes | Yes |
| --status | Yes | Yes |
| --criteria | No | Yes |
| --priority | No | Yes |
Restrictions:
in-progress or completeSee requirement-management.md section 2.4-2.5 for details.
Use /remove-requirement to remove pending requirements or modules.
Removing a requirement section:
/remove-requirement requirement "Legacy Support"
Removing a module:
/remove-requirement module legacy-api
Force removal (bypass checks):
/remove-requirement module in-progress-module --force
Removal restrictions:
pending or planned status--forceSee requirement-management.md section 2.6-2.7 for details.
Use /approve-plan to validate the plan and transition to Orchestration Phase.
Command:
/approve-plan
/approve-plan --skip-issues
Prerequisites (all must be met):
What happens on approval:
For complete details, see plan-approval-transition.md:
The plan phase uses a state file at .claude/orchestrator-plan-phase.local.md to track all planning progress.
For state file details, see state-file-format.md:
For troubleshooting issues, see troubleshooting.md:
| Error | Cause | Solution |
|---|---|---|
| State file not found | Planning not started | Run /start-planning first |
| Invalid status transition | Wrong status order | Follow: pending → in-progress → complete |
| Module has GitHub Issue | Cannot remove linked module | Use --force flag or close issue first |
| Approval prerequisites failed | Incomplete requirements | Mark all sections complete first |
| gh CLI auth failed | Not logged in | Run gh auth login |
This skill includes utility scripts for common operations.
Verify all prerequisites are met before approval:
python3 scripts/check_plan_prerequisites.py
python3 scripts/check_plan_prerequisites.py --fix-suggestions
Export the plan as a formatted markdown summary:
python3 scripts/export_plan_summary.py
python3 scripts/export_plan_summary.py --output plan-summary.md
Safely reset the plan phase (creates backup):
python3 scripts/reset_plan_phase.py --confirm
python3 scripts/reset_plan_phase.py --confirm --no-backup
# Step 1: Start planning
/start-planning "Build a REST API for user management"
# Step 2: Add modules
/add-requirement module "user-crud" --criteria "CRUD operations" --priority critical
/add-requirement module "auth-jwt" --criteria "JWT authentication" --priority high
# Step 3: Create USER_REQUIREMENTS.md manually
# Step 4: Mark sections complete
/modify-requirement requirement "Functional Requirements" --status complete
/modify-requirement requirement "Non-Functional Requirements" --status complete
/modify-requirement requirement "Architecture Design" --status complete
# Step 5: Verify and approve
/planning-status --verbose
/approve-plan
# Step 6: Begin orchestration
/start-orchestration
| Action | Command |
|---|---|
| Start planning | /start-planning "goal" |
| Check status | /planning-status |
| Add requirement section | /add-requirement requirement "Name" |
| Add module | /add-requirement module "name" --criteria "..." --priority high |
| Mark section complete | /modify-requirement requirement "Name" --status complete |
| Update module criteria | /modify-requirement module id --criteria "..." |
| Remove module | /remove-requirement module id |
| Approve plan | /approve-plan |
| Type | Allowed Status Values |
|---|---|
| Requirement sections | pending, in-progress, complete |
| Modules | planned, pending, in-progress, complete |
| Plan | drafting, reviewing, approved |
| Priority | Description |
|---|---|
| critical | Must have, blocking |
| high | Important, should have |
| medium | Normal priority (default) |
| low | Nice to have, can defer |
# Step 1: Start planning
/start-planning "Build a REST API for user management"
# Step 2: Add modules
/add-requirement module "user-crud" --criteria "CRUD operations" --priority critical
/add-requirement module "auth-jwt" --criteria "JWT authentication" --priority high
# Step 3: Create USER_REQUIREMENTS.md manually
# Step 4: Mark sections complete
/modify-requirement requirement "Functional Requirements" --status complete
/modify-requirement requirement "Non-Functional Requirements" --status complete
/modify-requirement requirement "Architecture Design" --status complete
# Step 5: Verify and approve
/planning-status --verbose
/approve-plan
# Step 6: Begin orchestration
/start-orchestration
# Check current status
/planning-status
# Update module criteria
/modify-requirement module auth-core --criteria "Support JWT and OAuth2" --priority critical
# Verify change
/planning-status --verbose
The following scripts automate RULE 14 (User Requirements Are Immutable) enforcement:
Manages requirement tracking documents and validates implementations against requirements.
| Command | Purpose | Usage |
|---|---|---|
init | Initialize requirements tracking structure | python scripts/eaa_requirement_analysis.py init --project-root <PATH> --project-name "<NAME>" |
parse | Parse requirements from user text | python scripts/eaa_requirement_analysis.py parse --input "<TEXT_OR_FILE>" |
report | Generate requirement issue report | python scripts/eaa_requirement_analysis.py report --project-root <PATH> --requirement-id REQ-001 --requirement-text "<TEXT>" --issue-type Feasibility --description "<ISSUE>" |
validate | Validate implementation against requirements | python scripts/eaa_requirement_analysis.py validate --project-root <PATH> --implementation <IMPL_PATH> |
docs_dev/requirements/ folder structureThis script enforces RULE 14: User Requirements Are Immutable. When issues arise:
The script is located at ../../scripts/eaa_requirement_analysis.py relative to this skill.
scripts/check_plan_prerequisites.py - Verify prerequisitesscripts/export_plan_summary.py - Export plan summaryscripts/reset_plan_phase.py - Reset plan phaseRelated Skills:
For additional error handling details, extended examples, resource links, and command output reference, see extended-examples-and-resources.md:
Converted and distributed by TomeVault — claim your Tome and manage your conversions.