القائمة
Validate a work item directory under docs/exec-plans/current/ by checking required files, headings, unresolved TODO markers, and markdown structure.
التثبيت باستخدام 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-validate |
| description | Validate a work item directory under docs/exec-plans/current/ by checking required files, headings, unresolved TODO markers, and markdown structure. |
| examples | ["$harness-validate docs/exec-plans/current/docs-import","$harness-validate docs/exec-plans/current/course-authoring/docs-import"] |
| when_to_use | ["Before handing work-item artifacts to implementation.","After editing PRD, FDD, plan, or design docs."] |
| when_not_to_use | ["The task is writing docs from scratch and no validation is needed yet."] |
Always load before validating:
references/validation_rules.mdreferences/link_validation_notes.mdreferences/definition_of_done.mdassets/templates/validation_report_template.mdscripts/validate_work_item.py