Start implementing a feature from the backlog with adaptive agent dispatch. Use when user wants to begin work on a backlog item, start implementation, or mentions a specific feature ID to work on.
You are executing the IMPLEMENT FEATURE workflow - a comprehensive feature kickoff process that ensures proper planning before any implementation begins.
Scan the feature directories to generate a live dashboard:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/run_dashboard.py <project_root> --stdout
This scans docs/features/*/ to show all features by status. If it fails or docs/features/ doesn't exist, the project hasn't been set up for feature tracking yet.
Note: To start a feature, create
docs/features/[id]/plan.md. The PostToolUse hook automatically updates the local DASHBOARD.md - do NOT edit it directly.
$ARGUMENTS
If no specific feature ID was provided above, you will help the user select from the backlog.
If $ARGUMENTS starts with cat:, filter the backlog to only show features matching that category (case-insensitive) and let the user select from the filtered list.
Features are stored in directories with status determined by file presence:
docs/features/
├── DASHBOARD.md # Auto-generated, read-only for Claude
├── my-feature/
│ ├── idea.md # Problem statement + metadata (backlog)
│ ├── plan.md # Implementation plan (in-progress)
│ └── shipped.md # Completion notes (completed)
└── another-feature/
└── idea.md
| Files Present | Status |
|---------------|--------|
| idea.md only | backlog |
| idea.md + plan.md | in-progress |
| idea.md + plan.md + shipped.md | completed |
Key Principles:
/feature-capture creates idea.md only (backlog status)/feature-plan adds plan.md (changes to in-progress)/feature-review-plan opens a draft PR for external plan review/feature-review-impl submits implementation for external code review/feature-ship adds shipped.md and merges the PR (changes to completed)This command orchestrates a 6-phase workflow:
| Phase | Name | Purpose | |-------|------|---------| | 1 | Feature Selection | Choose from backlog or validate provided ID | | 2 | Requirements Analysis | Deep dive with project-manager agent | | 3 | System Design | Architecture planning (adaptive based on feature type) | | 4 | Implementation Plan | Create detailed plan document | | 5 | Write plan.md | Write plan.md to transition to in-progress | | 6 | Kickoff Summary | Create todos and provide clear next steps |
See: selection.md
run_dashboard.py --stdout and find/select feature from Backlog sectionidea.md for full detailsAfter reading idea.md, check the state: field:
| State | Action |
|---|---|
| active (or absent) | Proceed normally |
| paused | Stop. Tell the user: "<id> is paused (waiting on: <pausedReason>). Resume with /feature-state <id> active before planning." |
| replaced | Stop. Tell the user: "<id> was replaced by <replacedBy>. Plan that one instead, or /feature-state <id> active to revive." |
| abandoned | Stop. Tell the user: "<id> was abandoned (<abandonedReason>). /feature-state <id> active to revive." |
In all stop cases, do NOT create a plan.md.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/statusline.py set <feature-id>
See: requirements.md
See: design.md
| Feature Type | Agents Used | |--------------|-------------| | Backend-Only | api-designer | | Frontend-Only | ux-optimizer + frontend-architect | | Full-Stack | api-designer + frontend-architect + integration-designer | | UI-Heavy | ux-optimizer → then full-stack agents | | Infrastructure | system-designer |
See: implementation.md
python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/run_dashboard.py <project_root>
Write plan.md with YAML frontmatter followed by content:
---
started: YYYY-MM-DD
---
# Implementation Plan: [Feature Name]
## Overview
Brief summary of what will be implemented...
## Implementation Steps
- [ ] Step 1: Description
- [ ] Step 2: Description
- [ ] Step 3: Description
## Technical Decisions
Key architectural choices made during design...
## Testing Strategy
How this feature will be tested...
## Risks & Mitigations
Any identified risks and how they'll be addressed...
The end-to-end workflow is:
/feature-capture → /feature-plan → /feature-review-plan → /feature-implement → /feature-review-impl → /feature-ship
The immediate next step after planning:
/feature-review-plan [feature-id] — create a feature branch, open a draft PR, submit the plan for external review (Gemini/Codex)/feature-review-plan [feature-id] --respond — address plan review feedback (repeat as needed)/feature-implement [feature-id] — write code following the approved plan/feature-review-impl [feature-id] — submit implementation for external code review/feature-review-impl [feature-id] --respond — address code review feedback (repeat as needed)/feature-ship [feature-id] — write shipped.md, merge the PR into dev, clean up the branchDo NOT skip review steps. /feature-review-plan gets the plan reviewed before coding. /feature-review-impl gets the code reviewed before shipping.
| Error | Resolution |
|-------|------------|
| DASHBOARD.md not found | Create it with generate-dashboard.sh |
| Feature not found | List available items, ask to select |
| Agent errors | Retry with more context or continue without that design phase |
| Directory missing | Create docs/features/ if needed |
| Already in progress | Ask if user wants to continue existing work |
By completing these 6 phases, you ensure:
Let's get started!
下载完整 Skill 目录，包含 SKILL.md 及所有相关文件
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer