Creates Codestable requirement files documenting problem, boundaries, rationale, and acceptance criteria.
npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-req
Please help me install this Agent Skill. Skill: cs-req Source: https://github.com/liuzhengdongfortest/CodeStable/tree/main/cs-req Command: npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-req
Documents the current state of a capability by creating a dedicated requirements file under codestable/requirements. It applies to backfill or update scenarios, ensuring each document clearly describes the problem, boundaries, and rationale for the capability. The output satisfies the frontmatter fields and the four prose sections without including implementation details or future plans.
Backfill or update a requirements document for a specific capability.
High-intent search queries and answers about installing and using this skill.
Requirements documentation should exclude implementation details and future roadmap plans to prevent confusion, ensuring the output strictly satisfies frontmatter fields and prose sections focused on current capability boundaries and rationale.
Separating requirements documentation from architecture and roadmap reduces confusion and supports non-technical readers during auditing and alignment phases.
The best way to document requirements without implementation details is to generate a dedicated file satisfying frontmatter fields and four prose sections, strictly describing the problem, boundaries, and rationale for the current capability state.
Yes, this requirements documentation approach works for non-technical readers by keeping requirements separate from architecture and roadmap, focusing solely on problem boundaries and rationale to support auditing and alignment.
You should keep requirements separate from architecture and roadmap plans to reduce confusion, ensure documents clearly describe current capability boundaries, and support non-technical readers during acceptance and auditing phases.
A key limitation when updating existing requirements files is that the output strictly excludes implementation details and future plans, focusing only on the current state, problem boundaries, and rationale for the specified capability.
sinositatoGather problem, user, scope, and success criteria into a markdown context file.
kevinnguyen271090Generate detailed technical implementation plans for software systems.
AutisticAFGenerate structured iOS app planning packages with product, technical, UI/UX, and distribution details.
bearbinaryConverts Markdown PRDs into structured JSON task files with progress tracking.
