메뉴
Generate a TechSpec artifact that translates a PRD into a concrete implementation plan. Use when the orchestrator routes the techspec phase or when the user asks to draft a technical specification. Do not use for PRD generation or task decomposition.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Verify whether Monozukuri can run with Codex in loop or full-auto workflows by checking agent availability, skill discovery, dry-run behavior, and the targeted Bats validation path. Use for Monozukuri Codex readiness, loop, agent doctor, or skill availability questions. Do not use for unrelated repositories or generic CI triage.
Audit a repository's local skills, agents, and instruction files for Codex compatibility and recommend only missing or redundant workflow assets. Use when the user asks whether skills are adapted to Codex, how to invoke project skills or agents, or which skills to install after scanning a repo. Do not use for ordinary code review or non-agent tooling.
Open a GitHub pull request via gh pr create with a body summarizing PRD goals, code changes, and test results. Use when the orchestrator routes the pr phase. Do not use for editing existing PRs or non-GitHub remotes.
Generate a PRD artifact for a monozukuri feature. Use when the orchestrator routes the prd phase or when the user asks to draft a feature PRD. Do not use for techspec/tasks generation or for editing an existing PRD.
Decompose a PRD and TechSpec into a structured tasks.json task list for monozukuri's code phase. Use when the orchestrator routes the tasks phase. Do not use for PRD or TechSpec generation.
Execute one PRD task end-to-end inside a git worktree — implement, verify acceptance criteria, and commit. Use when the orchestrator routes the code phase. Do not use for the tests, pr, or planning phases.
| name | mz-create-techspec |
| description | Generate a TechSpec artifact that translates a PRD into a concrete implementation plan. Use when the orchestrator routes the techspec phase or when the user asks to draft a technical specification. Do not use for PRD generation or task decomposition. |
| argument-hint | [feature-id] |
| version | 1.0.0 |
You are executing the techspec phase of monozukuri's autonomous feature loop.
$MONOZUKURI_WORKTREE/tasks/prd-$MONOZUKURI_FEATURE_ID/prd.md — every FR and NFR must be addressedCLAUDE.md, AGENTS.md, or the monozukuri learning storereferences/techspec-template.md — authoritative for section structurereferences/techspec-validation.mdWrite the TechSpec to $MONOZUKURI_WORKTREE/tasks/prd-$MONOZUKURI_FEATURE_ID/techspec.md.
The file MUST satisfy references/techspec-validation.md. The validator runs immediately after; failures trigger a reprompt.
files_likely_touched section must list at least one file path — this is a hard validator check.MAX_FILES files touched (value from the template). If the feature needs more, stop and flag it as two features.{{PLACEHOLDER}} — no placeholder survives.$MONOZUKURI_RUN_DIR/$MONOZUKURI_FEATURE_ID/prd.md.references/techspec-template.md.references/techspec-validation.md.CLAUDE.md and/or AGENTS.md for codebase conventions.Existing codebase patterns and files_likely_touched.Before starting, read $MONOZUKURI_MEMORY_DIR/MEMORY.md (if it exists) for shared feature context from the PRD phase. After writing the TechSpec, update $MONOZUKURI_TASK_MEMORY with the key architectural decisions and file scope recorded. If $MONOZUKURI_NEEDS_COMPACTION is non-empty and not none, run the mz-workflow-memory skill to compact memory files before continuing.