| name | implement-issue |
| description | Implement a GitHub issue in this repository by applying the shared `implement-specs` workflow with Oz-specific issue, spec-context, and summary-file handling. Use when issue details are provided in the prompt and the agent should produce the repository diff and a concise implementation summary, without creating commits or pull requests itself unless a cloud workflow explicitly asks for it. |
implement-issue
Implement a GitHub issue for this repository.
Overview
This skill is a thin Oz wrapper around the shared implementation skills:
implement-specsspec-driven-implementation
Use those shared skills as the base behavior unless this wrapper overrides them. Keep the same core model:
- approved product intent is the source of truth for user-facing behavior
- approved tech design is the source of truth for implementation shape
- specs and code should stay aligned as implementation evolves
The Oz-specific differences are:
- the primary input is a GitHub issue
- approved spec context may be supplied in
spec_context.md
- issue discussion must be fetched with the trusted GitHub context script named in the prompt
- the workflow expects a reusable markdown summary in
implementation_summary.md
- the workflow may also expect a structured PR metadata file in
pr-metadata.json
Inputs
Expect issue metadata in the prompt, including the issue number, title, labels, and assignees. The issue description, prior comments, and any triggering comment body are intentionally NOT inlined in the prompt. Contributors outside the organization can edit issue bodies and post comments, so inlining that content here would merge untrusted input with the workflow's own instructions.
Use the repository's script to pull that content on demand:
