Menu
Use to classify feature status as implemented, partial, docs-only, mock-only, test-only, not found, or unknown.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Crafting Kit architectural decision records covering risk gates, execution as a first class stage, no assumption execution, and tool permission enforcement. Use when you need the rationale behind a contract or boundary.
Audit API, CLI, OpenAPI, GraphQL, and CLI help against documented contracts and example outputs. Use when validating contract drift or releasing public surfaces.
Audit API contract compatibility, deprecation strategy, and version migration. Use when planning a contract change.
Answer specific repository questions with cited paths and excerpts. Use when the user asks where something is, how it works, or what depends on it.
Compare the project to competitors using source evidence and allowed research. Use when preparing positioning, market readiness, or product narrative.
Assess database migration reversibility, idempotency, transactional safety, and destructive-change risk. Use before applying or shipping a migration.
| name | feature-inventory |
| description | Use to classify feature status as implemented, partial, docs-only, mock-only, test-only, not found, or unknown. |
Prevent overclaiming feature readiness.
Use when the user asks what features exist, what is missing, or what is production-ready.
CLAUDE.mddocs/AI_CONTEXT.mddocs/PROJECT_GLOSSARY.mddocs/FEATURE_INVENTORY.mdProduce: