From hybrid-harness
Run the Hybrid Harness feature interview lane inside Claude Code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hybrid-harness:harness-interviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
이 스킬은 feature requirement를 한 번에 한 질문씩 줄여 가는 Claude-native interview lane이다.
이 스킬은 feature requirement를 한 번에 한 질문씩 줄여 가는 Claude-native interview lane이다.
새 interview를 시작할 때:
bash "${CLAUDE_PLUGIN_ROOT:-.}/scripts/harness-plugin-runner.sh" internal feature-init --idea "{{ARGUMENTS}}" --json
기존 interview를 이어갈 때:
bash "${CLAUDE_PLUGIN_ROOT:-.}/scripts/harness-plugin-runner.sh" internal feature-init --resume <interview-id> --json
questionPrompt, questionSchema, state, interviewId를 읽는다.questionPrompt를 기준으로 딱 한 개의 질문만 만든다.Round JSON shape:
{
"targeting": "goal",
"rationale": "Why this question matters",
"question": "Ask one question only",
"answer": "User answer",
"breakdown": {
"goal": { "score": 0.9, "justification": "Clear", "gap": "Clear" },
"constraints": { "score": 0.7, "justification": "Mostly clear", "gap": "Need boundary details" },
"criteria": { "score": 0.6, "justification": "Partly clear", "gap": "Need testable output" },
"context": { "score": 0.8, "justification": "Known", "gap": "Clear" }
},
"weakestDimension": "criteria",
"weakestDimensionRationale": "Output contract is still ambiguous"
}
그 다음 helper를 호출한다.
bash "${CLAUDE_PLUGIN_ROOT:-.}/scripts/harness-plugin-runner.sh" internal feature-apply-round --interview-id <interview-id> --round-file <round.json> --json
state.status가 completed가 되면 다음 단계는 seed-render다.nextCommand를 사용자에게 바로 안내한다.npx claudepluginhub hjsg1010/harness-js --plugin hybrid-harnessConducts short adaptive interview (2-6 questions) to clarify feature intent and business context, then launches /team-feature with compiled brief. Use for vague requests or explicit pre-build discussions.
Runs structured interview to align on technical constraints, scope boundaries, risk tolerance, and success criteria before feature implementation, refactoring, or non-trivial tasks via /plan-interview.
Conducts structured requirements-gathering interviews for software features/systems. Reads SPEC.md and context, asks numbered questions on purpose, technical design, UI/UX, edge cases, security, rollout. For deep requirement elicitation before specs/plans.