Run any Skill in Manus with one click

sdd-methodology

Stars1

Forks0

UpdatedApril 6, 2026 at 10:27

Guides agents through the Spec-Driven Development (SDD) lifecycle: specification authoring, technical planning, task decomposition, and implementation execution. Use when working on features that follow a structured development process, when creating specs, plans, or tasks, when the user mentions SDD, spec-driven, specification workflow, or when gating rules between phases need enforcement.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

attilaszasz

attilaszasz/weather-cli-demo-3

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	sdd-methodology
description	Guides agents through the Spec-Driven Development (SDD) lifecycle: specification authoring, technical planning, task decomposition, and implementation execution. Use when working on features that follow a structured development process, when creating specs, plans, or tasks, when the user mentions SDD, spec-driven, specification workflow, or when gating rules between phases need enforcement.

Spec-Driven Development Methodology

Lifecycle, phase gates, conventions, task format, and markers are defined in AGENTS.md (injected into every conversation context). Do not duplicate those rules here.

Project Bootstrap

Before feature delivery, a project can establish shared context:

Product Strategist (optional) — specs/prd.md + .github/sddp-config.md
Solution Architect (optional) — specs/sad.md + .github/sddp-config.md
Init — project-instructions.md + .github/sddp-config.md

Bootstrap does not change the strict feature delivery order in AGENTS.md.

Quality Philosophy: "Unit Tests for English"

Checklists validate the QUALITY of requirements, not implementation behavior:

✅ "Are error handling requirements defined for all API failure modes?"
❌ "Verify the API returns proper error codes"

The full quality framework is in references/quality-dimensions.md — read it only when performing quality analysis, checklist generation, or evaluating requirements quality.

More from this repository

same repository

analyze-compliance

attilaszasz/weather-cli-demo-3

Performs non-destructive cross-artifact consistency and quality analysis across spec, plan, and tasks. Also supports remediation mode to apply fixes. Use when running /sddp-analyze or when compliance auditing is needed.

2026-04-061

artifact-conventions

attilaszasz/weather-cli-demo-3

Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/<feature-folder>/ to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.

2026-04-061

autopilot-pipeline

attilaszasz/weather-cli-demo-3

Runs the full feature-delivery SDD pipeline end-to-end without user interaction. When called without arguments, auto-selects the first unchecked epic from specs/project-plan.md. Requires Autopilot enabled in config, a Product Document, and a Technical Context Document. Use when running /sddp-autopilot.

2026-04-061

clarification-strategies

attilaszasz/weather-cli-demo-3

Strategies for auditing specifications and reducing ambiguity. Use when running `/sddp-clarify` or whenever an agent needs to critique a requirement.

2026-04-061

clarify-spec

attilaszasz/weather-cli-demo-3

Clarify product, technical, and operational specs with targeted questions and write accepted answers into spec.md.

2026-04-061

deployment-operations

attilaszasz/weather-cli-demo-3

Create/refine project `specs/dod.md` as the canonical Deployment & Operations Document.

2026-04-061

name	sdd-methodology
description	Guides agents through the Spec-Driven Development (SDD) lifecycle: specification authoring, technical planning, task decomposition, and implementation execution. Use when working on features that follow a structured development process, when creating specs, plans, or tasks, when the user mentions SDD, spec-driven, specification workflow, or when gating rules between phases need enforcement.

Spec-Driven Development Methodology

Lifecycle, phase gates, conventions, task format, and markers are defined in AGENTS.md (injected into every conversation context). Do not duplicate those rules here.

Project Bootstrap

Before feature delivery, a project can establish shared context:

Product Strategist (optional) — specs/prd.md + .github/sddp-config.md
Solution Architect (optional) — specs/sad.md + .github/sddp-config.md
Init — project-instructions.md + .github/sddp-config.md

Bootstrap does not change the strict feature delivery order in AGENTS.md.

Quality Philosophy: "Unit Tests for English"

Checklists validate the QUALITY of requirements, not implementation behavior:

✅ "Are error handling requirements defined for all API failure modes?"
❌ "Verify the API returns proper error codes"

The full quality framework is in references/quality-dimensions.md — read it only when performing quality analysis, checklist generation, or evaluating requirements quality.