メニュー
8-layer readiness audit for Kapi platform. Audits actual code paths (manifest-transformer → runtime) and rewrites scorecard.md with honest percentages. Use when status.md grades feel optimistic, before /prd, or after significant code changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | scorecard |
| description | 8-layer readiness audit for Kapi platform. Audits actual code paths (manifest-transformer → runtime) and rewrites scorecard.md with honest percentages. Use when status.md grades feel optimistic, before /prd, or after significant code changes. |
| allowed-tools | Read, Grep, Glob, Write |
Update docs/operations/scorecard.md by auditing the actual code paths for all 8 layers.
Three columns, each as an honest percentage:
| Column | Question |
|---|---|
| Manifest → Config | Does lib/manifest-transformer.ts extract this layer's data and put it into TenantConfig? |
| Config → Runtime | Does the runtime code (chat route, tenant page, graph router) actually read and use that config? |
| End-to-End | Both columns working together. Not an average — if either side is broken, E2E is low. |
Scoring guidance:
For each layer (1-8), read the corresponding file at layers/{NN}-{name}.md. It lists the files to read and the key question to answer. Assess both sides of the wire independently, then write a one-sentence verdict that explains the biggest remaining gap.
After auditing all 8 layers, write the updated scorecard using the format in templates/output.md.
Be honest. If something is 0%, say 0%. The scorecard is used to prioritize sprint work — optimism defeats its purpose.
Read ../blackboard/posting.md for the posting convention. After completing the audit:
finding.finding.Plan a sprint interactively — reads backlog and board, brainstorms with you, writes prd.md + tasks.md.
Rate an agent's work. Records approve/reject/edit decision in kapi/decisions.yaml for HITL competence tracking.
End-of-session debrief. Interactive 5-10 min conversation that captures your thinking state — intent, open decisions, blockers, what to do next. Run before stepping away.
Pick the next unchecked task from the sprint and implement it with TDD. Reads board, posts available, implements, commits.
Quick write to the blackboard. Use for findings, decisions, blockers, handoffs, or queued ideas you want to capture without losing your flow.
Pre-sprint health check — git status, build, arch drift, infra, UX audit. Run before /prd to get a go/no-go verdict.