issue-authoring-workflow
author-issue
Shorthand: author-issue. Author a well-formed GitHub issue as the planner Technician, by consolidating durable evidence or shaping a new proposal from a durable decision, only with the Builder's explicit authorization in the current task. Check for duplicates read-only, resolve the repository's issue template or Garage's fallback, show the complete draft for confirmation, set only the approved title, body, and labels, and record the authoring role and source evidence. An authored issue never authorizes implementing it.
- Technician role
- planner
Technical details
- Source revision
- v0.1.0 · db2fcac
- Files
- SKILL.md, templates, templates/issue.md
Download the ZIP below, preserve the issue-authoring-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.
