Extend DevDocs projects with incremental features while preserving ID numbering and traceability.
npx skills add https://github.com/ab300819/skills --skill devdocs-feature
Please help me install this Agent Skill. Skill: devdocs-feature Source: https://github.com/ab300819/skills/tree/main/devdocs-feature Command: npx skills add https://github.com/ab300819/skills --skill devdocs-feature
This Skill enables teams to extend existing DevDocs projects by adding features while preserving numbering, consistency, and traceability across requirements, design, tests, and tasks.
Use /devdocs-feature "Add a small login enhancement" to start an incremental feature update process.
High-intent search queries and answers about installing and using this skill.
To add features without breaking documentation traceability, you need a workflow that enforces incremental design updates with strict ID continuation across requirements, system design, tests, and dev tasks. This process ensures aligned documentation and auditable versioning.
Incremental feature addition with F/US/AC numbering is a traceability method that extends existing project documentation by continuing requirement and use case IDs sequentially. It preserves consistency across system design, testing, and development tasks during controlled rollouts.
To maintain numbering consistency across requirements, system design, and tests, use a workflow that enforces strict ID continuation and step-by-step user confirmations. This ensures all documentation updates remain aligned and traceable during feature additions.
Yes, you can use this workflow for controlled rollouts with explicit user confirmations. It supports step-by-step collaboration across required sub-skills, ensuring auditable versioning and aligned documentation updates before any incremental feature change is finalized.
Yes, incremental feature addition requires coordinating multiple sub-skills like requirements and system design. The workflow supports step-by-step collaboration across requirements, system design, tests, and dev-tasks to ensure documentation continuity and strict traceability.
A limitation of using incremental documentation workflows for feature additions is the strict requirement for step-by-step user confirmations and ID continuation. Any deviation breaks traceability, making it unsuitable for rapid, undocumented prototyping outside the DevDocs project structure.
0xDarkMatterDetect stale project plans and suggest /plan commands from git activity.
bacocoImplement approved OpenSpec proposals by executing tasks and recording test evidence.
luisgustavooliveiraGenerate C4 diagrams, ERD, integration maps, and Spec Impact Matrix for legacy systems.
Young-ZBreak down requirements into MVP-first features and update the feature board.
