菜单
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.
用 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/.
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-architect |
| description | 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. |
| examples | ["$harness-architect docs/exec-plans/current/gradebook-overrides","$harness-architect docs/exec-plans/current/platform-modernization/gradebook-overrides"] |
| when_to_use | ["PRD exists and technical design decisions are needed.","The team needs concrete boundaries and contracts before planning or coding."] |
| when_not_to_use | ["PRD is missing (use $harness-analyze).","Task is direct implementation (use $harness-develop)."] |
Always load before writing:
references/persona.mdreferences/philosophy.mdreferences/approach.mdreferences/focus_areas.mdreferences/output_requirements.mdreferences/fdd_checklist.mdreferences/definition_of_done.mdreferences/validation.mdassets/templates/fdd_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/DESIGN.md, docs/OPERATIONS.md, and relevant files under docs/design-docs/docs/exec-plans/current/....<work_item_dir>/prd.md.<work_item_dir>/fdd.md.assets/templates/fdd_template.md as the section structure.harness.yml to determine whether feature flags, telemetry, performance requirements, code review, and issue tracking should appear by default.<skills_root> as the directory that contains the installed harness skills (architect/, 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_fddpython3 <skills_root>/requirements/scripts/requirements_trace.py <work_item_dir> --action master_validate --stage fdd_onlypython3 <skills_root>/validate/scripts/validate_work_item.py <work_item_dir> --check fdd<work_item_dir>/fdd.md.