spec

Automate six-phase requirement analysis and generate spec-driven documentation artifacts.

Updated Jun 19, 2020
One-click install
npx skills add https://github.com/xixiU/yu_config --skill spec-xixiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/xixiU/yu_config/tree/main/claude/skills/sdd-skills/spec
Command: npx skills add https://github.com/xixiU/yu_config --skill spec-xixiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven end-to-end requirement analysis and documentation workflow that unifies discovery, design, and delivery artifacts, ensuring alignment across stakeholders and reducing ambiguity.

Core Features & Use Cases

  • 6-phase workflow guiding: initialize workspace, understand needs, prepare worktree, design, define contracts and tests, plan tasks, and produce outputs.
  • Auto-generates core documents: spec.md, contracts.md, testcases.md, design.md, tasks.md, solution-design.html, repos.md, CLAUDE.md with cross-document references.
  • Supports knowledge-base integration and template-driven generation to accelerate onboarding and governance.
  • Enables traceability with ID-based linking (G-, NFR-, DEC-, API-, AC-, TC-, TASK- networks) across lifecycle.

Quick Start

Define the requirement using the SKILL.md frontmatter and run the skill to generate all workspace artifacts.

Frequently Asked Questions about spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end requirement analysis and documentation generation?▼

Requirement traceability uses ID-based linking across G, NFR, DEC, API, AC, TC, and TASK networks to connect lifecycle artifacts. It ensures alignment across stakeholders by maintaining cross-document references within the generated workspace outputs.

Can I use YAML frontmatter to drive requirement spec template generation?▼

Yes, you can integrate a knowledge-base to accelerate onboarding and governance during requirement analysis. This integration supports template-driven generation, enabling product teams to maintain alignment and reduce ambiguity across discovery, design, and deployment phases.

What is the best way to maintain traceability across product discovery and testing?▼

The best way to maintain traceability is implementing ID-based linking across G, NFR, DEC, API, AC, TC, and TASK networks. This connects lifecycle artifacts from discovery to deployment, ensuring cross-document references and stakeholder alignment.

Does the spec-driven workflow generate design and test case documentation automatically?▼

Yes, the spec-driven workflow automatically generates design and test case documentation including design.md, testcases.md, and contracts.md. It produces these outputs through a six-phase process covering needs understanding, design, and task planning.

What are the limitations of template-driven requirement documentation workflows?▼

Template-driven requirement documentation workflows require structured YAML frontmatter input to initialize the six-phase process. Limitations include dependency on predefined ID networks for traceability and the need for consistent knowledge-base integration to avoid ambiguity across generated artifacts.