oz-software-factory-template

Implement a fix or feature from a GitHub, Jira, Linear, or other issue-tracker issue by fetching issue context, inspecting the current codebase, making code changes, validating them, opening a GitHub pull request, and reporting progress back to the original issue.

Post a concise software-factory status update to a Slack channel via an incoming webhook after a factory phase completes a handoff. Use when a triage decision is made, a specs PR is opened, an implementation PR is opened, or an automated review verdict is published, and the SLACK_WEBHOOK_URL secret is configured.

Repo-specific code review guidance for this repository. Only the categories declared overridable below may be specialized here; the review output schema, severity labels, safety rules, and evidence rules are defined by the review-pr skill.

Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.

Audit a pull request diff for common security concerns (input validation, sanitization, authentication and authorization, secrets management, unsafe dependencies, and related risks) and fold findings into the same review.json produced by the base PR review. Use as a supplement to `review-pr` whenever a code PR is being reviewed.

Audit a product or tech spec pull request diff for high-level security concerns (threat surface, authentication and authorization model, trust boundaries, sensitive data handling, secrets and key management, dependency posture, and abuse or misuse cases) and fold findings into the same review.json produced by the base review. Use as a supplement to `review-pr` whenever a spec-only PR (changes limited to `specs/` or docs) is being reviewed.

Coordinate spec-driven development for a GitHub, Jira, Linear, or other issue-tracker issue moved to the Spec status (or given an equivalent label) by using write-product-spec and write-tech-spec, creating PRODUCT.md and TECH.md, opening a pull request, and routing the issue onward.

Repo-specific triage guidance for this repository. Only the categories declared overridable below may be specialized here; the core triage contract (states, output shape, guardrails) is defined by the triage skill.

Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured routing decision with exactly one target status. Use whenever the user asks to triage, classify, assess, prioritize, or route an issue, especially when an issue URL, key, or number is supplied in the prompt.