npx claudepluginhub luanrodrigues/ia-frmwrk --plugin bee-default[feature-name]Create a comprehensive implementation plan for a feature, with exact file paths, complete code examples, and verification steps. Plans are designed to be executable by engineers with zero codebase context. ## Usage ## Arguments | Argument | Required | Description | |----------|----------|-------------| | `feature-name` | Yes | Descriptive name for the feature (e.g., "user-authentication", "payment-webhooks", "email-notifications") | ## Examples ### Create a Feature Plan Creates a detailed plan for implementing OAuth2 authentication. ### Create an API Plan Plans the implementation ...
/write-planInforms user that the command is deprecated, will be removed in next major release, and directs to use superpowers:writing-plans skill instead.
/write-planNotifies that this command is deprecated and will be removed in the next major version, directing users to the superpowers:writing-plans skill instead.
/write-planGenerates a detailed implementation plan for the current task or project, breaking it down into bite-sized, actionable steps using a specialized writing skill.
/write-planCreates a structured implementation plan for a Symfony feature using the symfony:writing-plans skill.
/write-planInforms user that the command is deprecated, will be removed in next major release, and directs to use superpowers:writing-plans skill instead.
/write-planInforms user that the command is deprecated, will be removed in next major release, and directs to use superpowers:writing-plans skill instead.
Create a comprehensive implementation plan for a feature, with exact file paths, complete code examples, and verification steps. Plans are designed to be executable by engineers with zero codebase context.
/bee:write-plan [feature-name]
| Argument | Required | Description |
|---|---|---|
feature-name | Yes | Descriptive name for the feature (e.g., "user-authentication", "payment-webhooks", "email-notifications") |
/bee:write-plan oauth2-integration
Creates a detailed plan for implementing OAuth2 authentication.
/bee:write-plan rest-api-versioning
Plans the implementation of API versioning with migration path.
/bee:write-plan database-connection-pooling
Creates a step-by-step plan for implementing connection pooling.
A specialized planning agent (running on Opus model) is dispatched to:
The agent writes a comprehensive plan including:
Plan is saved to: docs/plans/YYYY-MM-DD-<feature-name>.md
After the plan is ready, you'll be asked:
| Option | Description |
|---|---|
| Execute now | Start implementation immediately using subagent-driven development |
| Execute in parallel session | Open a new agent session in the worktree for batch execution |
| Save for later | Keep the plan for manual review before execution |
Every plan passes the "Zero-Context Test" - executable with only the document:
Plans specify recommended agents for execution:
| Task Type | Recommended Agent |
|---|---|
| Backend (TypeScript) | bee:backend-engineer-typescript |
| Backend (PHP) | bee:backend-engineer-php |
| Frontend (BFF/API Routes) | frontend-bff-engineer-typescript |
| Testing | bee:qa-analyst |
| Reliability | bee:sre |
| Fallback | general-purpose (built-in) |
| Command/Skill | Relationship |
|---|---|
/bee:brainstorm | Use first if design is not yet validated |
/bee:execute-plan | Use after to execute the created plan |
bee:brainstorming | Design validation before planning |
bee:executing-plans | Batch execution with review checkpoints |
bee:subagent-driven-development | Alternative execution for current session |
Planning requires a validated design. Use /bee:brainstorm first to refine your concept before creating the implementation plan.
If the generated plan contains phrases like "implement the logic" or "add appropriate handling", the plan doesn't meet quality standards. Request revision with specific code examples.
This command is best run in a dedicated worktree created by the bee:brainstorming skill. You can still run it in main, but isolation is recommended.
If bee-dev-team plugin is not installed, execution falls back to general-purpose agents automatically. Plans remain valid regardless.
/bee:brainstorm first/bee:execute-plan insteadThis command MUST load the skill for complete workflow execution.
Use Skill tool: bee:writing-plans
The skill contains the complete workflow with: