openspec-sdd

Coordinate OpenSpec workflows for proposing, designing, implementing, and tracking feature changes.

3|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pax-k/pax-fullstack-harness --skill openspec-sdd-pax-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sdd
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/openspec-sdd
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill openspec-sdd-pax-k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage formal spec-driven development, ensuring that features, refactors, or product changes have a comprehensive proposal, design, and task-planned history.

Core Features & Use Cases

  • Formal Workflow Execution: Guides through a structured OpenSpec workflow for feature implementation.
  • OpenSpec Integration: Assists in maintaining proposal.md, design.md, and tasks.md for change tracking.
  • Use Case: For instance, when developing a new feature, it can help set up a formal workflow, track changes, validate implementation, and synchronize changes post-implementation.

Quick Start

Use the openspec-sdd skill to initiate a new OpenSpec change for your feature development.

Frequently Asked Questions about openspec-sdd

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

FAQPage Schema
How do I track feature changes using spec-driven development?

Spec-driven development tracks feature changes by maintaining structured proposal, design, and task documentation. This workflow assists in proposing, designing, implementing, and validating changes to ensure comprehensive history tracking.

What is the best way to maintain design and proposal documentation for new features?

Maintaining proposal and design documentation is best handled through a formal workflow that generates and updates specific files. This approach coordinates tracking through structured proposal, design, and task stages.

How do I set up a formal workflow for proposing and implementing code changes?

Setting up a formal workflow for code changes requires initiating a structured change process. This guides feature implementation by establishing proposal, design, and task tracking before validating and synchronizing the final changes.

Do I need specific scripts to validate and synchronize spec-driven development changes?

Yes, validating and synchronizing spec-driven development changes requires specific scripts. These scripts ensure the implementation matches the formal specifications and coordinate the workflow through its various stages.

Does OpenSpec workflow automation support refactoring and product changes?

Yes, OpenSpec workflow automation supports refactoring and product changes. It ensures these modifications have a comprehensive proposal, design, and task-planned history throughout the implementation process.