From frontend-craft
Generates a front-end implementation plan or comprehensive testing strategy based on user intent, saving reports to markdown files.
How this command is triggered — by the user, by Claude, or both
Slash command
/frontend-craft:fec-planThe summary Claude sees in its command listing — used to decide when to auto-load this command
Create a front-end plan before changing the code. Automatically divert traffic to implementation planning or test planning based on user intent. ## Intent recognition - **Implementation Planning** (default): Users need to dismantle components, design data flows, arrange directory structures, migration steps, and architecture plans. - **Test Planning**: The user clearly states "test plan", "test strategy", "coverage matrix", "test layering", "what to test", "risk-to-test", etc. - **Mixed**: Users have both implementation and testing requirements. If the intention is unclear, first ask the...
Create a front-end plan before changing the code. Automatically divert traffic to implementation planning or test planning based on user intent.
If the intention is unclear, first ask the user if they want to see the implementation plan or test strategy.
fec-architect.The implementation plan is saved to reports/architecture-proposal-YYYY-MM-DD-HHmmss.md.
Determine the scope:
Use the fec-testing-strategy Skill to create a test layering matrix:
Provide recommended test layers, priorities, recommended commands, responsibility skills and failure location evidence for each risk.
Indicate which risks only need to be covered by existing access control, which ones need new testing, and which ones are not covered yet and explain the reasons.
Delegate the fec-test-planner subagent to generate independent test plans when necessary.
Save the plan to reports/test-plan-YYYY-MM-DD-HHmmss.md:
# Front-end test plan
> Generation time: YYYY-MM-DD HH:mm
> Scope: ...
## Risk Overview
| Risk | Impact | Suggested Layer | Priority | Evidence |
| ---- | ------ | --------------- | -------- | -------- |
## Covering matrix
| Layer | What to Cover | Tooling / Command | Skill |
| ----- | ------------- | ------------------ | ----- |
## Execution order
## Items not covered and reasons
If the user requires to continue to implement the test, it will be diverted to the corresponding special skill or agent according to the matrix.
When users need to implement plans and test strategies at the same time:
test-plan-* independent reports will only be generated if the user explicitly requests complete coverage matrix.npx claudepluginhub bovinphang/frontend-craft/planDesigns actionable TDD-based implementation plans before coding, with optional clarification Q&A phase, checklists, and agent workflow guidance.
/planCreates an implementation plan before writing code for new features, architectural changes, or complex refactoring, including steps, risks, testing, and success criteria.
/hatch3r-test-planProduces a test plan specification from a feature or codebase scope, including coverage targets, risk-prioritized test cases, and structured todo.md entries for board tracking. Supports feature-scoped planning and coverage auditing modes.
/prp-planGenerates detailed feature implementation plan from description or PRD file path, with codebase analysis, pattern extraction, user story, and complexity assessment.
/planGenerates a detailed feature plan using the compiled layer. Checks for duplicates, identifies reuse, maps files to create/modify, and lists risks. Pauses for human approval before executing.
/planProduces a step-by-step technical implementation plan from an approved feature spec, identifying files, functions, and data flows without writing code.