القائمة
Convert an informal feature idea into a concise, implementation-ready PRD in a work item directory under docs/exec-plans/current/.
التثبيت باستخدام 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.
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.
| name | harness-analyze |
| description | Convert an informal feature idea into a concise, implementation-ready PRD in a work item directory under docs/exec-plans/current/. |
| examples | ["$harness-analyze docs/exec-plans/current/gradebook-overrides","$harness-analyze docs/exec-plans/current/platform-modernization/gradebook-overrides"] |
| when_to_use | ["A new work item needs a PRD.","A work item needs clarified scope, success criteria, or requirements traceability."] |
| when_not_to_use | ["The task is architecture design (use $harness-architect).","The task is direct implementation (use $harness-develop)."] |
Always load before drafting:
references/persona.mdreferences/approach.mdreferences/considerations.mdreferences/output_requirements.mdreferences/prd_checklist.mdreferences/definition_of_done.mdreferences/validation.mdassets/templates/prd_template.mdARCHITECTURE.md, harness.yml, docs/STACK.md, docs/TOOLING.md, docs/TESTING.md, docs/PRODUCT_SENSE.md, docs/FRONTEND.md, docs/BACKEND.md, docs/OPERATIONS.mddocs/exec-plans/current/....<work_item_dir>/prd.md.assets/templates/prd_template.md.requirements.yml.
Functional Requirements, include exactly: Requirements are found in requirements.ymlAcceptance Criteria, include exactly: Requirements are found in requirements.ymlharness.yml to decide whether feature flags, telemetry, performance requirements, code review, and issue tracking should be considered by default.harness.yml before deciding how it applies.<skills_root> as the directory that contains the installed harness skills (analyze/, 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 capture --bulk-file <bulk_payload_path>python3 <skills_root>/requirements/scripts/requirements_trace.py <work_item_dir> --action validate_structurepython3 <skills_root>/validate/scripts/validate_work_item.py <work_item_dir> --check prd<work_item_dir>/requirements.yml.<work_item_dir>/prd.md.<work_item_dir>/requirements.yml exists.