harness

Perform a concise, prioritized review of current code changes with concrete fixes, using the repository’s configured review policy and guides.

Seed a target repository with the required harness contract files and directory structure, and optionally draft initial repository-specific content when enough context is available.

Convert an informal feature idea into a concise, implementation-ready PRD in a work item directory under docs/exec-plans/current/.

Transform a PRD into a practical FDD in a work item directory under docs/exec-plans/current/ with concrete boundaries, interfaces, data impacts, and verification strategy.

Produce a slice-level detailed design doc at <work_item_dir>/design/<slice_slug>.md by mapping slice responsibilities, interfaces, edge cases, and tests to the work item requirements.

Implement one phase from a work item plan under docs/exec-plans/current/ using the repository contract as the source of truth.

Convert PRD and FDD into a dependency-ordered implementation plan in a work item directory under docs/exec-plans/current/ with explicit gates and verification notes.

Reconcile work-item docs after implementation drift by updating PRD, FDD, and plan artifacts under docs/exec-plans/current/ and re-validating them.

Execute a regression-safe, TDD-first bug-fix workflow using the repository’s configured issue intake, testing, and review rules.

Build a fast, low-ceremony prototype to validate an idea quickly, then report the shortest path to production hardening.

Manage deterministic FR and AC traceability in <work_item_dir>/requirements.yml across PRD, FDD, plan, and implementation proof artifacts.

Validate a work item directory under docs/exec-plans/current/ by checking required files, headings, unresolved TODO markers, and markdown structure.

Execute a lightweight work-item lane for small enhancements or refactors by generating a brief technical approach, pausing for approval, then implementing with repository-local rules.