Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

$pwd:

init-config

Name: Init Config
Author: microsoft

// 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).

Ejecutar en Manus

$ git log --oneline --stat

stars:29

forks:2

updated:9 de mayo de 2026, 20:02

SKILL.md

readonly

name	init-config
description	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).

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. If sdd-init.sh cannot 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 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.

Verification Mode

<SDD_INIT> verify

Parse 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-all

To show a diff for an outdated file:

<SDD_INIT> diff <target-path>

related-skills.json

mismo repositorio

pull-request.md

from "microsoft/devsquad-copilot"

Implementation finalization with PR. Use when implementation is complete and you need to commit, push, or open a pull request. Includes automated reviews and technical debt tracking. Do not use during implementation (use devsquad.implement), for standalone intermediate commits (use git-commit), or for branch creation (use git-branch).

2026-05-0929

documentation-style.md

from "microsoft/devsquad-copilot"

Formatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages. For work item content (titles, descriptions, comments on GitHub Issues or Azure DevOps), use the Content Style section of the `work-item-creation` skill.

2026-05-0929

harness-learnings.md

from "microsoft/devsquad-copilot"

Capture and consult codebase-specific learnings across the lifecycle. Use when an agent encounters a correction loop, review finding, test prerequisite, or recurring pattern that future sessions should know about. Also use at the start of implement, verify, or review to check for known patterns. Do not use for architecture decisions (use ADRs), for debugging the current failure (use debugging-recovery), or for one-time context that will not recur.

2026-05-0929

init-docs.md

from "microsoft/devsquad-copilot"

Verify and create SDD Framework documentation templates (feature spec, migration spec, envisioning, ADR templates). Use when initializing a project or checking if documentation templates are up to date. Do not use for configuration files (use init-config) or community files (use init-scaffold).

2026-05-0929

triage-workflow.md

from "microsoft/devsquad-copilot"

Label-based state machine for triaging issues and work items. Manages state transitions, generates durable triage artifacts, and supports resumable sessions. Use when triaging GitHub issues or Azure DevOps work items. Do not use for creating new work items from scratch (use work-item-creation) or for managing implementation workflow of already-triaged items (use work-item-workflow).

2026-05-0929

work-item-creation.md

from "microsoft/devsquad-copilot"

Rules and checklist for creating work items on GitHub Issues or Azure DevOps. Use when you need to create issues, user stories, tasks, epics, or features on the board. Do not use for platform configuration (use board-config), managing workflow of existing tasks (use work-item-workflow), or for comments on work items.

2026-05-0929

package.json

"author": "microsoft"

"repository": "microsoft/devsquad-copilot"

Abrir repositorio de GitHub Ver repositorios del creador

$ install --global

$ download --local

Ejecutar en Manus

$ useful --forSOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas15-1252L4

name	init-config
description	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).

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. If sdd-init.sh cannot be located via the discovery snippet below, inform the user to install/update the plugin.

Locating sdd-init.sh

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.

Verification Mode

<SDD_INIT> verify

Parse 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-all

To show a diff for an outdated file:

<SDD_INIT> diff <target-path>

init-config

Init Config

Managed Files

Important Constraints

Locating sdd-init.sh

Verification Mode

Creation Mode

Más de este repositorio

Más de este repositorio

Init Config

Managed Files

Important Constraints

Locating sdd-init.sh

Verification Mode

Creation Mode