ce-plan_skill

Overview

This skill transforms feature descriptions, bug reports, or improvement ideas into well-structured project plans that follow established conventions. It creates issue-ready markdown plans at configurable detail levels (MINIMAL, MORE, A LOT) and enforces repository naming, dating, and templating rules. The output is actionable and ready to file as a plan in docs/plans/ with traceable origins.

How this skill works

The skill first looks for a recent requirements document in docs/brainstorms/ created within the last 14 days and, if found, uses it as the authoritative source for planning. If no relevant origin exists, it runs a guided idea-refinement dialogue to clarify scope, constraints, and success criteria. It then performs parallel local research (repo patterns and documented learnings), decides whether external research is needed, consolidates findings, runs SpecFlow analysis to validate acceptance criteria, and emits a complete plan file with title, metadata, stakeholder analysis, dependencies, and chosen implementation detail level.

When to use it

• You have a feature idea, bug report, or improvement that needs an actionable plan
• You want plans that follow repository conventions for filenames and metadata
• You need to convert brainstorm documents into implementation-ready issues
• You want SpecFlow-validated acceptance criteria before opening an issue
• You need consistent plan detail levels for planning cadence or review

Best practices

• Provide a clear initial feature description; the tool will ask clarifying questions if it is empty
• If a brainstorm/requirements doc exists, let the skill use it as the origin to preserve decisions and blockers
• Choose the detail level (MINIMAL, MORE, A LOT) based on risk and team familiarity
• Supply supporting artifacts (logs, mockups, related PR/issue links) to speed planning
• Address any ‘Resolve Before Planning’ items in brainstorms first to avoid blocked plans

Example use cases

• Turn a concise feature note into a MORE-level issue plan ready for assignees and estimates
• Convert a recent brainstorm requirements doc into an A LOT comprehensive implementation plan (preserving origin decisions)
• Create a MINIMAL quick-fix plan for a small bug with reproduction steps and acceptance criteria
• Run local repo research and SpecFlow analysis to enrich acceptance criteria for a complex integration change
• Generate plan filenames and frontmatter that conform to the project’s daily sequence and discovery conventions