Create and maintain structured software design documentation with EARS notation.
npx skills add https://github.com/windschord/claude_skils --skill sdd-docs
Please help me install this Agent Skill. Skill: sdd-docs Source: https://github.com/windschord/claude_skils/tree/main/sdd-docs Command: npx skills add https://github.com/windschord/claude_skils --skill sdd-docs
This Skill eliminates common pitfalls in software development by providing a structured approach to documentation. It tackles ambiguous requirements, inconsistent design records, and unmanageable task breakdowns, ensuring clarity and traceability throughout your project. Stop wasting time on disorganized documentation and focus on building.
requirements.md, design.md, and tasks.md in a dedicated docs directory. This ensures all critical project information is centralized and easily accessible.requirements.md, design the database schema and service architecture in design.md, and then generate a detailed implementation plan in tasks.md, all while ensuring every step is clearly documented and traceable.Initialize the docs directory for your project.
High-intent search queries and answers about installing and using this skill.
Structured software design documentation organizes requirements, architecture, and tasks in a centralized docs folder. This Skill automatically sets up requirements.md, design.md, and tasks.md files, ensuring all critical project information is traceable and accessible throughout development.
EARS (Easy Approach to Requirements Syntax) is a structured method for writing precise, testable user stories and acceptance criteria. It reduces ambiguity in requirements by enforcing consistent phrasing, improving communication between teams and making requirements easier to validate.
Task management in design documentation converts feature requirements into granular, trackable tasks with acceptance criteria and dependencies marked. This Skill generates an actionable implementation plan in tasks.md that simplifies project planning and enables progress monitoring.
Yes, structured design documentation works for both new projects and incremental improvements. This Skill supports template-driven creation and edits across requirements, design, and tasks files, maintaining cross-document consistency whether you're starting fresh or enhancing existing systems.
Technical design documentation captures system architecture, component designs, data models, and key technical decisions. This preserves institutional knowledge, streamlines developer onboarding, and ensures architectural decisions remain traceable and accessible to the team.
Disorganized documentation leads to ambiguous requirements, inconsistent design records, and unmapped task breakdowns, creating rework and knowledge loss. Structured documentation eliminates these pitfalls by centralizing information, ensuring clarity, and maintaining traceability throughout the development lifecycle.
HiveSpaceTeamInitialize backend development tasks for HiveSpace features with implementation contracts.
kang-swImplement ticket phases with task tracking, testing, and documentation updates.
xxyjArchive completed software change sets and generate learning documentation.
dralgorhythmDocument architectural decisions using ADR format with Title, Status, Context, Decision, Rationale, and Consequences.