npx claudepluginhub data-wise/craft --plugin craftplan/# Feature Planning Plan and scope new features with structured breakdown. ## Usage ## What This Does 1. **Analyzes feature request** and context 2. **Breaks down into tasks** with estimates 3. **Identifies dependencies** and risks 4. **Creates actionable plan** with acceptance criteria ## Planning Outputs | Output | Description | |--------|-------------| | User Stories | Who, what, why format | | Tasks | Concrete implementation steps | | Estimates | Time estimates per task | | Dependencies | Blocking items | | Risks | Potential issues | | Acceptance | How to verify completion | ## ...
/featureOrchestrates full feature development cycle: PRD with product-owner, visual style options, architecture, code, QA, docs, delivery via phased agents and gates.
/featureAutomates Rails feature/chore from Linear URL or description: creates branch, gathers context, implements/tests/lints/i18n, drafts PR, monitors CI.
/featureCreates a lightweight feature-focused PRD via guided interactive interview (5-8 rounds) optimized for new features in existing products, saving to docs/prd/{slug}.md
/featureExecutes Mermaid flowchart workflow: two Analyze-Design(D3)-Develop(G2→G2.5→G3)-Release cycles, using Task for sub-agents, AskUserQuestion at diamonds, and F5 gates.
/featureGuides through 10-stage new feature development workflow from brainstorming to code review, pausing for user confirmation at each stage.
/featureImplements features from Linear/Jira issues or prompts using minimal iteration cycles and structured workflow with resume detection, producing code increments, tests, reviews, and PRs. Accepts [issue-key-or-prompt] [--provider=linear|jira|prompt] [--silent=true|false].
Plan and scope new features with structured breakdown.
/craft:plan:feature <feature_description>
| Output | Description |
|---|---|
| User Stories | Who, what, why format |
| Tasks | Concrete implementation steps |
| Estimates | Time estimates per task |
| Dependencies | Blocking items |
| Risks | Potential issues |
| Acceptance | How to verify completion |
--scope <level> - MVP, full, or enterprise--format <type> - markdown, jira, github--output <file> - Save plan to file--include-tests - Include test planning# Plan a feature
/craft:plan:feature "user profile page with avatar upload"
# MVP scope only
/craft:plan:feature "search functionality" --scope mvp
# Include test planning
/craft:plan:feature "payment integration" --include-tests
# Export as GitHub issue
/craft:plan:feature "notifications" --format github
Feature Plan: User Profile with Avatar Upload
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
User Stories:
1. As a user, I want to view my profile so I can see my account info
2. As a user, I want to upload an avatar so I can personalize my account
3. As a user, I want to edit my profile details so I can keep info current
Tasks:
Backend (8 hours)
├── [ ] Create profile API endpoint (2h)
├── [ ] Add avatar upload handler (2h)
├── [ ] Implement image resizing (2h)
└── [ ] Add profile update endpoint (2h)
Frontend (6 hours)
├── [ ] Create profile page component (2h)
├── [ ] Add avatar upload widget (2h)
└── [ ] Implement edit form (2h)
Infrastructure (2 hours)
├── [ ] Set up S3 bucket for avatars (1h)
└── [ ] Configure CDN (1h)
Dependencies:
- S3 bucket must be created first
- Auth system must be in place
Risks:
⚠ Image upload may need size limits
⚠ CDN cache invalidation for avatar changes
Acceptance Criteria:
✓ User can view their profile page
✓ User can upload avatar (jpg, png, max 5MB)
✓ Avatar displays in header and profile
✓ User can edit name, bio, email
Total Estimate: 16 hours (2 days)
Works with:
/craft:plan:sprint - Sprint planning/craft:arch:plan - Architecture planning/craft:git:branch - Create feature branch