$ loading_
Initialize projects or verify and generate up-to-date SDD documentation templates.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "init-docs" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/init-docs/SKILL.md 2. Save it as ~/.claude/skills/init-docs/SKILL.md 3. Reload skills and tell me it's ready
Please initialize SDD Framework documentation templates for this new project, including feature spec, migration spec, envisioning, and ADR templates, and explain the purpose of each file.
A complete set of documentation templates, base content structure, and explanations of each template's purpose.
Please check whether the SDD documentation templates in the current repository are complete and up to date, identify missing or outdated items, and provide the required updates.
A template audit result listing missing or outdated documents, with update recommendations or replacement content.
The project only has partial requirements docs. Please add the missing SDD template skeletons, keep naming consistent, and suggest a recommended directory structure.
Standard skeletons for the missing templates, consistent naming, and a clear recommended documentation structure.
Manage 4 SDD Framework documentation templates.
| File | Purpose |
|---|---|
docs/features/TEMPLATE.md | Feature specification template |
docs/migrations/TEMPLATE.md | Migration specification template |
docs/envisioning/TEMPLATE.md | Envisioning document template |
docs/architecture/decisions/ADR-TEMPLATE.md | Architecture Decision Record template |
NEVER create, copy, or recreate files under
.github/plugins/. The plugin folder is managed externally. Ifsdd-init.shcannot be located via the discovery snippet below, inform the user to install/update the plugin.
The plugin can be installed in several locations (workspace, runtime env vars, ~/.vscode/agent-plugins/..., ~/.copilot/agent-plugins/...). Use the locate-sdd-init.sh helper to resolve the absolute path of sdd-init.sh once, then reuse it in every subsequent command. The discovery snippet:
for h in \
.github/plugins/devsquad/hooks/locate-sdd-init.sh \
"${COPILOT_PLUGIN_ROOT:-}/hooks/locate-sdd-init.sh" \
"${CLAUDE_PLUGIN_ROOT:-}/hooks/locate-sdd-init.sh" \
"$HOME/.vscode/agent-plugins/github.com/microsoft/devsquad-copilot/.github/plugins/devsquad/hooks/locate-sdd-init.sh" \
"$HOME/.copilot/agent-plugins/github.com/microsoft/devsquad-copilot/.github/plugins/devsquad/hooks/locate-sdd-init.sh" \
"$HOME/.copilot/installed-plugins/devsquad-copilot/devsquad/hooks/locate-sdd-init.sh"; do
if [ -n "$h" ] && [ -f "$h" ]; then
SDD_INIT="$("$h" 2>/dev/null || true)"
[ -n "$SDD_INIT" ] && [ -f "$SDD_INIT" ] && { echo "FOUND: $SDD_INIT"; exit 0; }
fi
done
echo "MISSING"
exit 1
Capture the absolute path printed after FOUND: and substitute it for <SDD_INIT> in every command below. Bash variables do not persist across tool calls, so use the literal path string.
<SDD_INIT> verify
Parse the JSON output. Each entry in docs has file, status (up-to-date, outdated, missing), and optionally summary.
To create or update specific files:
<SDD_INIT> create <target-path>
For bulk operations:
# Create only missing files
<SDD_INIT> create-missing
# Create missing + overwrite outdated
<SDD_INIT> update-all
To show a diff for an outdated file:
<SDD_INIT> diff <target-path>
Systematically triage failures and fix broken builds or unexpected runtime issues.
Design and review software architecture diagrams for clearer, documentation-friendly visuals.
Create, switch, and verify Git branches before starting implementation work.
Verify and create standard community and governance files for new projects.
Verify assignee, dependencies, priority, and capacity before starting a work item.
Standardize formatting and writing style for project Markdown documentation.
Initialize and verify SDD project config files and keep instructions up to date.
Guide users to co-author docs, proposals, and specs through iterative refinement.
Write and maintain technical docs, from READMEs to API and runbook guides.
Improve OSS growth strategy, conversion docs, and contributor acquisition workflows.
Generate a structured .instructions.md file for project rules or conventions.
Set up complete project scaffolds and development environments in VS Code.