repo-discovery-init

Files (1)

• SKILL.md

SKILL.md (first lines)

# repo-discovery-init

Purpose: discover the real project structure before any project-specific Copilot setup is generated.

## Use When

- A repository has no `.mastermind` layer yet.
- You need to detect active languages and source roots.
- You need to identify backend, frontend, test, and Python/ML roots.
- You need to decide what belongs in neutral `.github` vs project-specific `.mastermind`.

## Required Outputs

1. Detected language and framework inventory.
2. Candidate source roots and test roots.
3. Candidate project paths for `.mastermind/project-paths.json`.
4. Signal whether graph artifacts already exist.
5. Signal whether `.mastermind/agent-paths.json` already exists.

## Minimum Checklist

- Detect top-level code roots.
- Detect test roots and BDD locations.
- Detect whether project-specific runtime artifacts still leak into `.github`.
- Detect whether repository-specific standards are already encoded in instructions or skills.
- Produce a short list of items that require explicit user confirmation.

## Do Not

- Invent standards.
- Create project-specific agents before discovery is complete.
- Assume a graph exists if only partial artifacts are present.

From ArkadiuszSieracki/mastermind-agentic-sdlc-vscode-copilot, Apache-2.0.

More from ArkadiuszSieracki/mastermind-agentic-sdlc-vscode-copilot