engineering-discovery-workflow
eng-discovery
Shorthand: eng-discovery. Investigate an existing software system before implementation. Use for repository discovery, current-state audits, capability inventories, gap analysis, cross-layer tracing, and evidence-backed engineering investigation where the system must not be changed. Discovery is complete only after the report is durably documented in the originating GitHub issue or in an accessible durable artifact directly linked from that issue.
- Technician role
- discovery
Technical details
- Source revision
- v0.1.0 · db2fcac
- Files
- SKILL.md, templates, templates/issue.md
Download the ZIP below, preserve the engineering-discovery-workflow/ directory, and place it in a skill directory supported by your harness.
Hand-placed skills are unmanaged. Canonical skills resolve project choices through garage config validate, so configuration-dependent steps still need a valid project configuration and garage on PATH. Directly requested discovery does not require configuration for its discovery-applicability decision.
From a project with valid configuration and declared skill targets, install and verify the complete embedded canonical skill set, together with the manuals the project adopts:
garage config validate garage skills install garage skills verify
The CLI supports user-scope targets for Claude Code, Codex, and Copilot CLI, not individual-skill or project-scope installs. Harness path behavior was confirmed on macOS; Linux and Windows harness behavior remains unconfirmed. Existing unmanaged or modified copies require explicit replacement consent and a backup. See skill installation.
