Extract and categorize requirements from CONTEXT.md into v1, v2, and out of scope.
npx skills add https://github.com/Tromml/kimchi --skill kimchi-requirements
Please help me install this Agent Skill. Skill: kimchi:requirements Source: https://github.com/Tromml/kimchi/tree/main/plugins/kimchi/skills/requirements Command: npx skills add https://github.com/Tromml/kimchi --skill kimchi-requirements
This Skill transforms raw context into a structured, prioritized list of requirements, ensuring clarity and focus for development.
Use the kimchi:requirements skill to categorize requirements from the CONTEXT.md file.
High-intent search queries and answers about installing and using this skill.
Requirement categorization separates features into 'v1 (Must Have)', 'v2 (Next Iteration)', and 'Out of Scope' buckets. This prioritization mechanism works by transforming raw project context into a structured list, ensuring development focuses only on initial release needs.
Assigning acceptance criteria to must-have features involves generating testable conditions for each 'v1' requirement during the scoping phase. This ensures every prioritized item has a clear, verifiable definition of done before development begins.
Generating a structured requirements list involves extracting information from a CONTEXT.md file and producing a REQUIREMENTS.md file. This process assigns unique IDs and testable acceptance criteria specifically to prioritized v1 requirements for immediate development clarity.
No, you do not need to investigate your codebase to categorize requirements. The scoping process strictly adheres to avoiding codebase investigation during this stage, relying entirely on the provided context document to define v1, v2, and out of scope items.
Acceptance criteria should be defined exclusively for 'v1 (Must Have)' requirements to ensure they are testable, while 'Out of Scope' items are simply categorized and excluded. This distinction is established during the initial product development scoping phase.
Space-DinosaursConsolidate session data into AGENTS.md, MEMORY.md, and .agentic/context.md.
romiluz13Gather and analyze project requirements to define user stories and acceptance criteria.
danilonovaisvConvert raw ideas into structured design plans with formal documentation.
mgkyawzayyaGenerate step-by-step implementation plans with acceptance criteria and a consolidated plan.md.
