From lite-sdd
Lite-SDD new project initialisation. Use when the user is starting a new Spec-Driven Development project from scratch — creating the agent instruction file (CLAUDE.md for Claude Code, .github/copilot-instructions.md for GitHub Copilot), the README skeleton, and the spec/plan layout. Also use when the user asks how to set up a project for the lite-sdd workflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lite-sdd:lite-sdd-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bootstrap a project for the lite-sdd workflow. Three things get set up:
Bootstrap a project for the lite-sdd workflow. Three things get set up:
README.md — so a human reading the repo understands the workflow.specs/ layout — owned by lite-sdd-overview (route there, don't restate it).This skill is additive. The instruction file and the README may already exist, possibly written by other skills. Never overwrite them. Add a clearly delimited lite-sdd block and leave everything else untouched.
Add, don't replace. Write the lite-sdd content inside marker comments so it is re-runnable and separable from other skills' content:
<!-- lite-sdd:start -->
...lite-sdd block...
<!-- lite-sdd:end -->
On re-run, replace only what is between the markers — never duplicate the block.
Leave other content alone. Do not touch instructions written by other skills unless they contradict lite-sdd or create an ambiguity (e.g. they say specs live somewhere else).
Any change to existing content must be approved by the user. Adding the delimited block to a file is fine. Editing or removing anything already in the file — including resolving a contradiction — requires showing the user the exact change and getting their go-ahead first.
Pick the file for the agent in use (set up both if the project uses both):
| Agent | File |
|---|---|
| Claude Code | CLAUDE.md (repo root) |
| GitHub Copilot | .github/copilot-instructions.md |
If neither exists, create it with just the lite-sdd block. If it exists, append the
block per the additive rule. The block declares the methodology and tells the agent
to load lite-sdd-overview every session:
<!-- lite-sdd:start -->
## Spec-Driven Development (lite-sdd)
This project follows the lite-sdd methodology: specifications in `specs/` are the
functional source of truth, kept in lockstep with the code.
- Load the `lite-sdd-overview` skill at the start of every session for the project
layout, feature numbering, and global principles.
- Use `lite-sdd-specify` to write or update a spec before coding.
- Use `lite-sdd-implement` to plan the implementation and keep it in sync.
<!-- lite-sdd:end -->
Add a lite-sdd section to the repo's root README.md (create it if absent) so a
human contributor knows where specs live and how the loop runs. Same additive rule
and markers:
<!-- lite-sdd:start -->
## Spec-Driven Development
Specs live in [`specs/`](./specs), one folder per feature, numbered in blocks of a
hundred (one block per application). Each `spec.md` is the functional source of
truth: write or update it before changing the code, then implement against it.
<!-- lite-sdd:end -->
Create the specs/ directory and seed its README.md index — the table of contents
a human or agent reads to navigate the specs. The structure, numbering, and naming
rules are owned by lite-sdd-overview → ## Repository layout — follow them there
rather than restating them here.
At init time there are no features yet, so write a minimal index with the title and a
one-line intro, ready for lite-sdd-specify to fill as features are added. Use the
format and the three-level tree shown in lite-sdd-overview → ### The specs/README.md index:
# Specifications
Table of contents for every app, feature, and user story in this project.
| Anti-pattern | Correct approach |
|---|---|
Overwriting an existing CLAUDE.md / README / Copilot file | Append a delimited lite-sdd:start … :end block |
| Editing content written by another skill on sight | Only on contradiction/ambiguity, and only with explicit user approval |
| Resolving a contradiction silently | Show the user the exact change and get approval first |
| Re-running this skill duplicates the block | Replace only what is between the markers — idempotent |
Restating the specs/ layout in the instruction file | Route to lite-sdd-overview |
Inventing feature entries in specs/README.md at init | Seed an empty index; lite-sdd-specify adds entries as features are written |
lite-sdd-overviewlite-sdd-specifylite-sdd-implementProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub tchinnin/lite-sdd --plugin lite-sdd