init-config
Skill50 starsChanged 16 days agoMITView on GitHub
Verify and create SDD Framework configuration files (.github/copilot-instructions.md, instructions, coding-guidelines, markdownlint). Use when initializing a project or checking if configuration files are up to date. Do not use for documentation templates (use init-docs) or community files (use init-scaffold).
Files
Init Config
Manage 10 SDD Framework configuration and instruction files.
Managed 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 |
Important Constraints
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.
Locating sdd-init.sh
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 1Capture 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.
Verification Mode
<SDD_INIT> verifyParse the JSON output. Each entry in config has file, status (up-to-date, outdated, missing), and optionally summary.
Creation Mode
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-allTo show a diff for an outdated file:
<SDD_INIT> diff <target-path>In this repository26 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- .github/plugins/devsquad/hooks/templates/.github/copilot-instructions.mdCopilot instructions
- adr-workflowSkill
- board-configSkill
- complexity-analysisSkill
- debugging-recoverySkill
- deep-clarificationSkill
- diagram-designSkill
- documentation-styleSkill
- domain-glossarySkill
- engineering-practicesSkill
- git-branchSkill
- git-commitSkill
- harness-learningsSkill
- init-docsSkill
- init-scaffoldSkill
- lsp-setupSkill
- next-taskSkill
- pull-requestSkill
- quality-gateSkill
- reasoningSkill
- security-reviewSkill
- test-disciplineSkill
- triage-workflowSkill
- work-item-creationSkill
- work-item-workflowSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

