Convert informal engineering requests into phased plans saved as markdown files.
npx skills add https://github.com/kolatts/claude-marketplace --skill sunny-plan
Please help me install this Agent Skill. Skill: sunny:plan Source: https://github.com/kolatts/claude-marketplace/tree/main/plugins/sunny/skills/plan Command: npx skills add https://github.com/kolatts/claude-marketplace --skill sunny-plan
Create structured engineering plans from vague work requests and save them as markdown files in the repository. This Skill infers scope (Story vs Epic), writes concise phased plans with an approach, lists files likely affected, and includes verification steps; it can also generate JIRA user stories from the plan. It is triggered when someone asks to plan out a feature, scope a ticket, or break down engineering work into actionable steps.
Plan the new feature for OAuth2 login by turning the feature description into a phased plan and save it to planning/.
High-intent search queries and answers about installing and using this skill.
To break down a feature request, transform it into a structured, phased plan with concrete approaches, affected files, and verification steps. This process infers scope to guide effort and saves the finalized plan as a markdown file in the repository for traceability.
When scoping engineering work, Story vs Epic sizing is inferred based on the request's overall scope and schedule. Stories represent smaller targeted tasks, while Epics denote larger bodies of work requiring more extensive phased planning and breakdown.
Generating JIRA user stories from a codebase feature plan takes a finalized phased plan and drafts corresponding tickets to streamline task creation. This bridges repository planning with issue tracking by structuring actionable work items.
Yes, you can save feature planning documentation directly into your repository. The finalized plan is written to a planning/ directory as a markdown file, ensuring traceability and keeping engineering plans alongside the affected codebase.
No, you do not need a specific project management tool to create phased plans. Planning is triggered by natural-language requests across codebases to structure work, with JIRA integration serving as an optional step for drafting user stories.
pinkroosteraiCreate issues or feature requests from natural language descriptions.
AnastasiyaWDecompose project plans into Markdown tickets with acceptance criteria.
chiruu12Analyze commit history, work patterns, and code quality metrics for engineering retrospectives.
OpalBoltConvert project plans into verifiable issues using tracer-bullet vertical slicing.
