$ loading_
Initialize and verify SDD project config files and keep instructions up to date.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "init-config" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/init-config/SKILL.md 2. Save it as ~/.claude/skills/init-config/SKILL.md 3. Reload skills and tell me it's ready
Initialize SDD Framework configuration for this new project. Create .github/copilot-instructions.md, instructions, coding-guidelines, and markdownlint, and fill them with sensible default team standards.
Creates the required config files with baseline standards suitable for a new project.
Check whether the SDD configuration files in the current repository are complete and up to date. Identify anything missing, outdated, or inconsistent, and suggest updates.
Returns a configuration audit with missing items, issues found, and recommended fixes or updates.
Update the SDD configuration files based on the current project structure, refining development instructions, coding guidelines, and Markdown lint rules for team collaboration and code review.
Produces updated configuration content that makes project standards more consistent, actionable, and maintainable.
Manage 10 SDD Framework configuration and instruction files.
| File | Purpose |
|---|---|
.github/copilot-instructions.md | Pragmatic senior engineer guidelines |
.github/instructions/adrs.instructions.md | ADR creation and management guidelines |
.github/instructions/envisioning.instructions.md | Envisioning document guidelines |
.github/instructions/specs.instructions.md | Feature spec guidelines |
.github/instructions/tasks.instructions.md | Task list guidelines |
.github/instructions/migration-specs.instructions.md | Migration spec guidelines |
.github/instructions/migration-tasks.instructions.md | Migration task guidelines |
.github/instructions/documentation-style.instructions.md | Markdown formatting rules |
.github/docs/coding-guidelines.md | Fundamental values, mandatory rules, code style |
.markdownlint.yaml | Markdown linting configuration |
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 config 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.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Verify and create standard community and governance files for new projects.
Standardize formatting and writing style for project Markdown documentation.
Generate a structured .instructions.md file for project rules or conventions.
Generate or update chat customization files for AI coding agents.
Guide users to co-author docs, proposals, and specs through iterative refinement.
Set up complete project scaffolds and development environments in VS Code.
Set up complete project scaffolds and dev environments in VS Code.
Generate standardized Git commits from diffs with logical grouping support.