القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | harness-plan |
| description | 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. |
| examples | ["$harness-plan docs/exec-plans/current/gradebook-overrides","$harness-plan docs/exec-plans/current/platform-modernization/gradebook-overrides"] |
| when_to_use | ["PRD/FDD are present and implementation planning is required.","A phased execution plan is needed before coding."] |
| when_not_to_use | ["PRD/FDD are missing (use $harness-analyze and $harness-architect first).","Task is direct coding (use $harness-develop)."] |
Always load before planning:
references/persona.mdreferences/approach.mdreferences/planning_considerations.mdreferences/output_requirements.mdreferences/plan_checklist.mdreferences/definition_of_done.mdreferences/validation.mdassets/templates/plan_template.md<work_item_dir>/prd.md<work_item_dir>/fdd.mdARCHITECTURE.mdharness.ymldocs/STACK.mddocs/TOOLING.mddocs/TESTING.mddocs/PRODUCT_SENSE.mddocs/FRONTEND.mddocs/BACKEND.mdprd.md and fdd.md.plan.md from the plan template.harness.yml and repository docs to decide which cross-cutting concerns must be planned explicitly.<skills_root> as the directory that contains the installed harness skills (plan/, requirements/, validate/, etc.). Do not resolve script paths relative to the repository or current working directory.python3 <skills_root>/requirements/scripts/requirements_trace.py <work_item_dir> --action verify_planpython3 <skills_root>/requirements/scripts/requirements_trace.py <work_item_dir> --action master_validate --stage plan_presentpython3 <skills_root>/validate/scripts/validate_work_item.py <work_item_dir> --check plan