Menu
Create a .plan.md file when the user asks to make a plan, create a plan, write a plan, or similar
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Pins and manages per-project Flutter SDK versions with FVM (Flutter Version Management). Use when the project has or needs a .fvmrc or .fvm/ directory, when contributors need a reproducible Flutter SDK, when installing FVM, pinning or switching the Flutter version, wiring FVM into VS Code or Android Studio, configuring CI to honor .fvmrc, or troubleshooting "wrong Flutter version" symptoms.
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
Build a competitive positioning matrix and strategy canvas when the user asks to analyze competitors, compare products, or assess competitive landscape
Audit project dependencies for risk when the user asks to check dependencies, audit packages, review dependency health, check for vulnerabilities, or assess supply chain risk
Analyze product metrics and identify trends when the user asks to review metrics, analyze KPIs, or assess product health
Audit a feature for WCAG 2.1 AA compliance using POUR principles when the user asks to check accessibility, audit a11y, or verify WCAG compliance
| name | create-plan |
| description | Create a .plan.md file when the user asks to make a plan, create a plan, write a plan, or similar |
| author | chalk |
| version | 1.0.0 |
| metadata-version | 3 |
| allowed-tools | Read, Glob, Write |
| argument-hint | [plan description] |
| read-only | false |
| destructive | false |
| idempotent | true |
| open-world | false |
| user-invocable | true |
| tags | planning, tasks, execution |
| capabilities | planning.create, chalk.plans |
| activation-intents | create plan, make a plan, plan this |
| activation-events | user-prompt |
| activation-artifacts | .chalk/.cursor/plans/**, AGENTS.md |
| risk-level | low |
Follow the plan creation conventions defined in .chalk/.cursor/plans/ and any project AGENTS.md if present.
New plans go into the unsorted backlog (root of .chalk/.cursor/plans/) by default unless the user specifies a column (todo/, inprogress/, testing/, done/).
.chalk/.cursor/plans/ (not subfolders) to find the highest numbered plan. The next plan number is that number + 1..chalk/.cursor/plans/<number>_<slug>.plan.md.<number>_<snake_case_slug>.plan.md
Every plan has YAML frontmatter (name, overview, todos with id/content/status) and a markdown body with # Title, ## Objective, ## Architecture, ## File Changes, and ## Key Design Decisions sections.
Refer to AGENTS.md for the full spec and format details.