Menu
Implement one phase from a work item plan under docs/exec-plans/current/ using the repository contract as the source of truth.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | harness-develop |
| description | Implement one phase from a work item plan under docs/exec-plans/current/ using the repository contract as the source of truth. |
| examples | ["$harness-develop docs/exec-plans/current/gradebook-overrides phase=2","$harness-develop docs/exec-plans/current/platform-modernization/gradebook-overrides phase=2"] |
| when_to_use | ["PRD, FDD, and plan exist and implementation is requested for a specific phase.","Work requires tests and validation closure."] |
| when_not_to_use | ["Required planning inputs are missing.","Task is low-ceremony prototype work (use $harness-prototype)."] |
Always load before coding:
references/persona.mdreferences/approach.mdreferences/coding_guidelines.mdreferences/stack_practices.mdreferences/ui_boundaries.mdreferences/development_checklist.mdreferences/output_requirements.mdreferences/definition_of_done.mdreferences/validation.mdassets/templates/phase_execution_record_template.mdARCHITECTURE.md, harness.yml, docs/PRODUCT_SENSE.md,docs/FRONTEND.md, docs/BACKEND.md, docs/CODEREVIEW.md when enabled, and the work item docsprd.md, fdd.md, plan.md, and relevant design/*.md files.<skills_root> as the directory that contains the installed harness skills (develop/, validate/, etc.). Do not resolve script paths relative to the repository or current working directory.python3 <skills_root>/validate/scripts/validate_work_item.py <work_item_dir> --check all before coding.docs/TOOLING.md and docs/TESTING.md.harness.yml, run at least one $harness-review round after tests pass.python3 <skills_root>/validate/scripts/validate_work_item.py <work_item_dir> --check all after implementation.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.
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.