aidev_axon_7

Create Product Requirements Documents (PRDs) from feature requests using a required clarify-plan-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a PRD, product requirements document, product spec, feature requirements document, or requirements artifact that should be saved as tasks/prd-[feature-name]/prd.md.

Create implementation task lists and individual task files from an existing PRD and Tech Spec. Use when Codex is asked to write, generate, create, draft, or update feature tasks, implementation tasks, task breakdowns, delivery plans, or task files based on tasks/prd-[feature-name]/prd.md and tasks/prd-[feature-name]/techspec.md.

Create implementation-ready Technical Specifications from existing PRDs using a required analyze-research-clarify-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a Tech Spec, technical specification, implementation specification, architecture spec, or engineering plan based on tasks/prd-[feature-name]/prd.md and save it as tasks/prd-[feature-name]/techspec.md.

Fix documented QA bugs for a feature by reading bugs.md, qa.md, PRD, Tech Spec, and tasks; planning fixes by severity; implementing root-cause fixes; adding regression tests; validating with project tests and Playwright for UI bugs; and updating bugfix artifacts. Use when Codex is asked to fix bugs, resolve QA findings, address failed QA, or complete bugfix work in tasks/prd-[feature-name]/.

Execute QA validation for a completed feature against its PRD, Tech Spec, and tasks using Playwright MCP, accessibility checks, visual review, bug documentation, and a final QA report. Use when Codex is asked to test, QA, validate, approve, reject, or verify a feature implementation in tasks/prd-[feature-name]/.

Execute a code review for implemented work by analyzing git diff, reading modified files, checking project rules and skills, verifying Tech Spec and task adherence, running tests, identifying code quality issues, and saving a code review report. Use when Codex is asked to review code, validate implementation quality, approve changes, or produce codereview.md for a feature or project change.

Execute the next available implementation task from a PRD task folder. Use when Codex is asked to implement, execute, start, continue, or complete a task using tasks/prd-[feature-name]/prd.md, techspec.md, tasks.md, and individual task files, then mark the task complete after verification.

Create Product Requirements Documents from feature ideas or product requests. Use when Codex is asked to create, draft, generate, or save a PRD; turn a feature request into requirements; define goals, user stories, scope, user experience, or product constraints; or create files under tasks/prd-[feature-name]/prd.md.

Create implementation task plans and task files from complete PRDs and TechSpecs. Use when Codex is asked to create, draft, generate, or save tasks; break a PRD and technical specification into deliverable implementation tasks; define subtasks, success criteria, test requirements, relevant files, rule conformance, or skill conformance; or create files under tasks/prd-[feature-name]/tasks.md and tasks/prd-[feature-name]/[num]_task.md.

Create implementation-ready Technical Specifications from complete PRDs. Use when Codex is asked to create, draft, generate, or save a tech spec; translate a PRD into architecture and implementation guidance; define interfaces, models, endpoints, integration points, testing strategy, observability, sequencing, or technical risks; or create files under tasks/prd-[feature-name]/techspec.md.

Execute bug fixes from documented QA bugs for implemented features. Use when Codex is asked to fix bugs from bugs.md, resolve QA failures, create regression tests, update bugs.md and qa.md, validate fixes with project tests or Playwright MCP, or produce a bugfix report for tasks/prd-[feature-name]/.

Execute quality assurance validation for implemented features against PRDs, TechSpecs, and task files. Use when Codex is asked to run QA, validate an implementation, verify requirements, run E2E tests with Playwright MCP, check accessibility, perform visual checks, document bugs, create bugs.md, or create qa.md under tasks/prd-[feature-name]/.

Execute code review for implementation changes against TechSpecs, task files, project rules, and project skills. Use when Codex is asked to review code, analyze git diff, verify tests, check rules compliance, validate TechSpec or task adherence, identify code smells, or create codereview.md at the project root or under tasks/prd-[feature-name]/.

Execute the next available implementation task from a project task list. Use when Codex is asked to pick up a pending task, work from tasks/prd-[feature-name]/tasks.md, implement a PRD or tech-spec task, continue a task backlog, or complete and mark project tasks done end to end.