Provide spec templates, interview questions, complexity signals, and codebase exploration procedures.
npx skills add https://github.com/sequenzia/agent-tools --skill sdd-specs
Please help me install this Agent Skill. Skill: sdd-specs Source: https://github.com/sequenzia/agent-tools/tree/main/plugins/sdd/skills/sdd-specs Command: npx skills add https://github.com/sequenzia/agent-tools --skill sdd-specs
Spec creation and review often require gathering templates, interview questions, complexity signals, and codebase exploration steps from disparate sources. This skill provides a centralized, reusable reference to streamline spec work and maintain consistency across projects.
Load this skill as a reference during spec creation or review to access templates, questions, signals, and codebase exploration procedures.
High-intent search queries and answers about installing and using this skill.
Spec templates provide standardized structures for requirements and technical considerations, ranging from high-level to detailed and full-tech depths to match project scope and risk assessment needs.
Assess complexity signals by evaluating codebase exploration procedures and interview question banks, identifying risk factors and scope depth to ground your technical specifications in real project constraints.
Conduct codebase exploration by applying structured procedural guidance and integration references to analyze existing code patterns, ensuring your spec accurately reflects the current technical architecture.
Interview question banks support spec creation by providing structured prompts to extract problem analysis requirements, ensuring you gather consistent technical considerations across high-level and detailed documentation.
The spec reference supports reviewing by applying standardized templates, complexity signals, and recommendation patterns to assess specification depth, consistency, and technical accuracy across different projects.
Standardized templates require adaptation to fit specific codebase patterns and project contexts, as rigid application without exploring integration references may miss unique architectural constraints during spec creation.
trevorbyrumInterview users to define project scope, assumptions, and constraints.
robin-liConvert finalized development plans into GitHub Issues and linked project boards.
cxnaiveIndexes source code repositories into interactive knowledge graphs of symbols and call chains.
jayhjenkinsGuide an interactive eight-phase session to create and validate Product Requirements Documents.
