forge

Produce a concrete implementation plan for a standalone Task or Epic takeover ticket. Use when a Jira Task/Epic is approved for Task Takeover planning and needs target files, implementation steps, tests, and repository scope.

Read-only qualitative review for Task Takeover implementations before PR creation. Use after task takeover execution completes.

Decompose a Technical Specification into implementable Epics with technical plans. Use when asked to break down features, create epics, or plan implementation.

Break down Epic implementation plans into concrete, actionable Tasks. Use when decomposing Epics into implementation units.

Implement code changes according to Task specifications. Use when executing implementation Tasks.

Produce a concrete implementation plan for a bug fix from an approved RCA and selected fix approach. Use when the team has selected a fix option and needs a detailed plan before implementation.

Revise a bug fix implementation plan based on reviewer feedback. Use when the team has reviewed a plan and requested changes before approving.

Evaluate a bug ticket for completeness before starting analysis. Use when triaging bug reports to determine if enough information is present to begin investigation.

Qualitative code review for bug fixes — verifies root-cause alignment and test coverage before PR creation. Use after implement-task completes for bug tickets.

Validate an RCA for correctness and evidence quality before presenting it to the engineering team. Use after analyze-bug produces an rca.json.

Re-perform a root cause analysis after receiving feedback from the engineering team. Use when the team has reviewed an RCA and requested changes.

Detects documentation files that have become stale due to code changes and applies minimal targeted updates. Builds an identifier checklist from the diff, greps documentation for matches, evaluates candidates in two passes, and edits confirmed stale docs in-place.

Generate a structured Product Requirements Document (PRD) from raw requirements. Use when asked to create a PRD, product spec, requirements document, or feature definition.

Generate a Technical Specification with behavioral acceptance criteria from a PRD. Use when asked to create a spec, technical specification, or detailed requirements.

Analyze CI failures by fetching logs and producing a structured fix plan. Use before attempting automated CI fixes.

Analyze CI failures by fetching logs and producing a structured fix plan. Use before attempting automated CI fixes.

Apply CI fixes from a pre-analyzed fix plan. Use after analyze-ci has produced a structured plan.

Generate Root Cause Analysis (RCA) for bugs using TDD methodology. Use when analyzing bug reports.

Analyze PR review comments against the current codebase, classify every comment, and produce a structured plan. No comment may be silently dropped.

Run codegen, lint, then review local code changes for breaking issues and fix them in-place. Use before PR creation to catch critical problems early.

Perform AI code review analyzing pull requests for quality, security, and specification alignment. Use for PR reviews.