메뉴
Inspect LeanHarness feature state and summarize current specs, discovery, plans, tasks, checks, blockers, and next actions. Use when the user invokes /lh-status or asks what is happening in the current LeanHarness work.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | lh-status |
| description | Inspect LeanHarness feature state and summarize current specs, discovery, plans, tasks, checks, blockers, and next actions. Use when the user invokes /lh-status or asks what is happening in the current LeanHarness work. |
| disable-model-invocation | true |
| allowed-tools | Read, Glob, Grep, TaskCreate, TaskUpdate |
Inspect LeanHarness artifacts and summarize the current state of feature work. Read-only by default. Does not modify files unless the user explicitly asks to repair state.
Accept any of:
all: summarize all known features by stateblocked, planned)Examples:
/lh-status
/lh-status F001
/lh-status all
/lh-status blocked
On Claude Code: As the very first action (before any Read, Bash, or other tool call), call TaskCreate for each step below all at once, so the user sees the full roadmap immediately. Before starting each step, call TaskUpdate to mark it in_progress. After completing each step, call TaskUpdate to mark it completed. Use the activeForm field as the spinner label.
On OpenCode: Before starting each step, emit a step header:
---
**Step N/M — <Step Name>**
where N is the current step number and M is the total step count.
Steps:
| # | Subject | activeForm |
|---|---|---|
| 1 | Read state.json + feature dirs | Reading state |
| 2 | Analyze consistency + blockers | Analyzing consistency |
| 3 | Report | Reporting |
.lh/state.json if present..lh/features/ if present.spec.mddiscovery.mdboundary.jsonplan.mdtasks.mdchecks.mdresult.mdtask-summaries/cavebus.logstate.json or inferred from artifacts)For each feature, show:
F001draft, specified, discovered, planned, building, checking, pass, needs-fix, blockedFor multiple features, use a summary table:
| Feature | Title | Status | Next Step |
|---|---|---|---|
| F001 | Password reset | planned | /lh-build F001 |
| F002 | Billing fix | specified | /lh-discover F002 |
If .lh/state.json and feature folders disagree:
specified but plan.md exists, suggesting it is planned").Every /lh-status run must end with:
Run the full LeanHarness feature workflow for an existing codebase: specify, discover, plan, build, and check. Use when the user invokes /lh-do with a feature request or asks Claude Code to complete a feature through LeanHarness.
Execute LeanHarness feature tasks with bounded context, boundary discipline, tests, compact summaries, and verification evidence. Use when the user invokes /lh-build or wants Claude Code to implement planned tasks.
Verify a LeanHarness feature against acceptance criteria, changed files, risk gates, review findings, and command evidence. Use when the user invokes /lh-check or wants a final pass, needs-fix, or blocked verdict.
Perform LeanHarness on-demand discovery for an existing codebase and produce a focused change boundary. Use when the user invokes /lh-discover or needs relevant files, tests, commands, constraints, risks, and unknowns before planning.
Create a LeanHarness implementation plan and task list from an existing feature spec, discovery report, and change boundary. Use when the user invokes /lh-plan or needs planned tasks before building.
Create or update a LeanHarness feature specification from a user request. Use when the user invokes /lh-spec or wants to define goal, non-goals, acceptance criteria, constraints, assumptions, and verification expectations before implementation.