create-a-plan
Create a Plan Skill
This skill runs a structured technical interview to turn a rough idea or an existing spec into a detailed, implementable plan. The output is organized for parallel execution: foundations first, then independent workstreams, then merge and integration.
Invocation
The user will provide one of:
- A path to a spec or plan file (for example:
SPEC.md,PLAN.md,RFC.md) - A rough description of what they want to build
- A feature request or problem statement
Output is always written to PLAN.md in the repo root.
Process
Phase 0: Preflight
- If a file path is provided, read it first and note goals, non-goals, constraints, and gaps.
- Confirm you will produce
PLAN.mdas the output in the repo root. IfPLAN.mdalready exists, update it rather than creating a new file.
More from cartridge-gg/controller
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
42codegen
Regenerate GraphQL types from API schema. Use when API schema has changed, GraphQL queries/mutations added or modified, or type errors in API calls.
39validate-before-merge
Run full validation to ensure code is ready for merge. Use before merging PRs, when asked to validate readiness, or as a final check before requesting review.
35update-storybook-snapshots
Update Storybook visual regression snapshots after intentional UI changes. Use when visual tests fail due to expected changes, or when asked to update snapshots.
35test
Run appropriate test suites based on changed files or user request. Use to run tests intelligently based on the type of changes.
34pre-commit-check
Run all pre-commit checks before committing changes. Use to manually verify changes pass all quality gates before committing.
34