devflow-discovery

Discovery

Ground the work in what exists before changing anything — and pay the discovery cost once per repo, not once per task.

Step 0 — Profile cache (always first)

Check docs/devflow/profile.md:

• Exists + fresh → use it as the discovery result. Do task-specific lookups only (Glob/Grep for symbols named in the task). Skip steps 1, 4, 5, 6.
• Exists + stale (any build file's recorded hash changed, or referenced paths are gone) → refresh only the stale sections, bump the hashes.
• Missing → run full discovery below, then write the profile.

Freshness: the profile records a hash line per build file it derived from (sha1 package.json, sha1 pom.xml, …). Compare before trusting.

Full discovery (profile miss)

Read budget: standard ≤10 file reads, deep ≤20. Glob/Grep before Read.

1. Repo type — root build files: package.json, pom.xml, build.gradle*, *.csproj/*.sln, pubspec.yaml, pyproject.toml, docker-compose*.yml, Makefile. Note frameworks/languages.
2. Relevant files — Glob/Grep for symbols/routes/tables named in the task. 5–15 paths max.
3. Existing patterns — read 1–3 sibling files: naming, layering, error handling, test style.
4. Verification commands — derive from build files; per-stack recipes in ${CLAUDE_PLUGIN_ROOT}/skills/devflow-discovery/stack-recipes.md (load only for this step).
5. Test layout — test directory + one test file to mirror.
6. Constraints — CLAUDE.md, CONTRIBUTING.md, README.md hard rules.

Write the profile

docs/devflow/profile.md (committed — shared with the team):

# devflow project profile
<!-- hashes: <sha1> package.json | <sha1> pom.xml -->

## Stack
…frameworks, languages, versions…

## Verification
- per-task: `<cmd>`
- full suite: `<cmd>`
- lint/typecheck/build: `<cmd>`

## Conventions
…naming, layering, error handling, test style — bullets…

## Test layout
…paths, example test file…

## External sources
…sibling repo paths / shared libraries (if confirmed)…

## Hard rules
…from CLAUDE.md / CONTRIBUTING.md…

Keep ≤1 screen. Update it whenever discovery learns something durable; it replaces re-discovery for every later phase and session.

Output

Context packet (compact bullets): stack, key files with line ranges, conventions, verification commands, open questions, assumptions. This packet travels verbatim to later phases — make it self-sufficient.

Stop. Do not implement from this skill.