sdd-init

Generates SDD documents from existing codebases through inspection and user interviews.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-init-alessioscarfone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/AlessioScarfone/aine-copilot-plugins/tree/main/src/sdd-team/skills/sdd-init
Command: npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-init-alessioscarfone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adopting Specification-Driven Development on a legacy or existing project requires writing PRD, architecture, and UX documents from scratch, which is time-consuming when the knowledge only exists in the code. ## Core Features & Use Cases - Codebase Reconnaissance: Systematically inspects README, build manifests, CI/CD configs, and source structure to derive project type, tech stack, entry points, and UI presence. - Gap-Filling Interview: Asks only the questions that cannot be answered from the code, in a single consolidated round. - Document Generation Pipeline: Dispatches subagents to generate prd.md, architecture.md, and conditionally ux.md plus an HTML prototype, then initializes sdd-tracker.yml. - Use Case: You inherit a brownfield web app with no documentation. Run this skill to reverse-engineer the PRD and architecture docs from the source code and a short interview, so the full SDD workflow can proceed. ## Quick Start Ask the AI to initialize SDD on this existing project by inspecting the codebase and generating the shared SDD documents. ## Quick Start Use sdd-init to bootstrap SDD documentation on my existing codebase.

Frequently Asked Questions about sdd-init

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

FAQPage Schema
How do I adopt spec-driven development on an existing codebase?▼

Run sdd-init on the project. It inspects the codebase, asks a single round of gap-filling questions, then generates prd.md, architecture.md, and optionally ux.md, plus initializes the sdd-tracker.yml file.

What documents does SDD initialization generate?▼

It generates prd.md and architecture.md in the shared artifacts folder, ux.md and an HTML prototype only if a UI layer is detected and confirmed, and sdd-tracker.yml to track artifact status.

Can I use sdd-init for a new greenfield project?▼

No. sdd-init is designed for brownfield projects with existing code but no SDD documents. For greenfield projects, use the standard SDD workflow starting with the PRD and architecture skills directly.

What happens if SDD documents already exist in my project?▼

The skill stops immediately and informs you that shared documents already exist. It never overwrites existing docs; you must delete the shared folder first to re-initialize from scratch.

When is the UX document generated during SDD init?▼

The UX phase runs only when a UI layer is detected during codebase reconnaissance and the user confirms UX documentation is needed. It is never generated for projects without a UI, even if requested.