krprashantpk/code-story
CodeStory searches remote work items, authors and exports backlog stories, agrees on high-level technical plans, and turns approved work items into implemented, verified code. Includes shared coding standards.
Use when the user wants to create a new backlog story, capture a feature/refactor idea, draft user-facing intent, or write the description and acceptance criteria for a piece of work. Produces ONLY the story background (Description + Acceptance Criteria) under .backlog/work-items/. Does NOT plan or implement code. Triggers include "create a story", "add a backlog item", "draft a UC", "capture this idea". For technical breakdown use the code-story-technical-plan skill; for execution use the code-story-implementer skill.
Use when the user wants to execute, implement, build, or close out a planned work item or backlog story. Reads an approved standalone plan under .backlog/technical-plan/ or a legacy story with an embedded Technical Implementation Plan, makes code/doc changes, runs tests, and appends an Implementation Summary and Closing Comment to the plan or legacy story. Triggers include "implement this story", "execute the plan", "do UC7", "ship this", and "close out the story". Requires an approved technical plan.
Use when the user wants a high-level technical implementation plan for any supplied work item, story, issue, bug, feature, or task. Collaboratively develops an architecture-led approach, verifies version-sensitive decisions against current official documentation, and incorporates user feedback until explicitly approved. Only then creates .backlog/technical-plan/<story-title-slug>.md.