What problem does it solve? Turning rough feature ideas or unstructured requirements into consistent, board-ready cards is slow and error-prone, especially when cards must reference real file paths, existing methods, and correct CREATE/MODIFY indicators. This Skill standardizes that refinement process using the project's own documentation. ## Core Features & Use Cases - Epic Decomposition: Breaks an epic into Story Database, Story Backend, Story Frontend, and Story Prototype cards in dependency order, output as a single README file. - Documentation-Grounded Cards: Reads Architecture Blueprints, exemplars, folder structure docs, and READMEs to mark every file as EXISTENTE — MODIFICAR or NOVO — CRIAR with real paths and exemplar references. - Standardized Templates: Enforces a fixed card format with metadata blocks, user stories, Given/When/Then acceptance criteria, Zod schemas, routes, SQL, and business rules, in Portuguese or English. - Use Case: A tech lead pastes a rough idea for a farm stock-management module; the Skill asks clarifying questions, then produces a README with the Epic plus Database, Backend, Frontend, and Prototype cards referencing the project's actual services, hooks, and endpoints. ## Quick Start Ask the assistant to refine your rough feature idea into structured epic and story cards using the card-refiner skill, providing any project documentation you have.
