\n\nQuick Guide: Specify every endpoint as a complete contract — method, path, auth requirement, request shape, success response, and an error catalog with a status per condition. Specify schema as exact columns with constraints, relationships, indexes, and a migration strategy. Order the middleware pipeline explicitly. Apply a framework only when the spec touches its artifact class — an endpoint-only change needs no schema section.
\n
<critical_requirements>
\n\n\nAll specifications must be grounded in the codebase's real routes, schemas, and middleware — reference specific files with line numbers
\n
(You MUST give every endpoint a complete contract: method, path, auth requirement, request shape, success response shape, and an error catalog)
\n(You MUST state the auth requirement per endpoint — which middleware, which permission — never \"endpoints should be protected\")
\n(You MUST specify schema as exact columns with types, constraints, relationships, indexes, and a migration strategy)
\n(You MUST catalog error responses per endpoint — a status code per condition with its response body shape)
\n(You MUST apply each framework only when the spec touches its artifact class — an unused section is omitted, never filled)
\n</critical_requirements>
\nAuto-detection: API spec, endpoint design, REST contract, request response shape, database schema spec, migration plan, middleware ordering, auth requirements, error catalog
\nWhen to use:
\nWhen NOT to use:
\nKey patterns covered:
\nDetailed Resources:
\n<decision_framework>
\nApply a framework only when the spec touches its artifact class. The per-artifact section templates live in examples/core.md.
\nDoes the spec add or change an endpoint?\n├─ YES → API Contract section (Patterns 1-3), one block per endpoint\n└─ Does it add or change tables, columns, or indexes?\n ├─ YES → Database Schema section (Patterns 4-5), one block per table\n └─ Does it add or reorder middleware?\n ├─ YES → Middleware Requirements section (Pattern 6)\n └─ NO → None of these frameworks applies; do not force one in\n| Failure | \nConsequence | \n
|---|---|
| \"User data\" instead of an exact shape | \nThe implementer and each consumer resolve the ambiguity differently | \n
| \"Protected\" instead of named middleware | \nAuth drifts per endpoint; a route ships public that should not be | \n
| No error catalog | \nConsumers cannot branch; every client wraps calls in generic catch | \n
| Schema as prose | \nConstraint decisions deferred to the migration author | \n
| No migration strategy | \nIrreversible change discovered during deploy | \n
| Endpoint set larger than the requirement | \nUnused surface to secure, test, and maintain | \n
| No named consumers | \nA shape change ships without knowing who breaks | \n
</decision_framework>
\n<red_flags>
\nHigh Priority Issues (a spec with one of these is incomplete):
\nMedium Priority Issues:
\nCommon Mistakes:
\nGotchas & Edge Cases:
\n</red_flags>
\n<critical_reminders>
\n\n\nAll specifications must be grounded in the codebase's real routes, schemas, and middleware
\n
(You MUST give every endpoint a complete contract: method, path, auth requirement, request shape, success response shape, and an error catalog)
\n(You MUST state the auth requirement per endpoint — which middleware, which permission)
\n(You MUST specify schema as exact columns with types, constraints, relationships, indexes, and a migration strategy)
\n(You MUST catalog error responses per endpoint — a status code per condition with its response body shape)
\n(You MUST apply each framework only when the spec touches its artifact class — an unused section is omitted, never filled)
\nFailure to specify these contracts produces APIs whose implementers invent shapes, whose consumers break on drift, whose auth gaps ship silently, and whose migrations cannot be rolled back.
\n</critical_reminders>
\n","files":[{"path":"examples/core.md","sizeBytes":8890,"isText":true},{"path":"SKILL.md","sizeBytes":14575,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-29T15:30:41.937632Z","sha256":"B07DCA2BD88C5C0563497CABDAB05A7D75DD74800650F63CF30FD2615C930D91","sizeBytes":8103},"review":null,"source":{"repositoryUrl":"https://github.com/agents-inc/skills","path":"dist/plugins/meta-planning-api-planning/skills/meta-planning-api-planning","license":"MIT","commit":"3a51ef571e996b18294bf776d53dbdad26de0617","subtreeSha":"DFC4CD161C20266444EC944D99AB26E522FA7B74F59B241D7B1BB7D0A43AE98E","lastSyncedAt":"2026-09-29T15:27:48.914434Z"},"reviewedAt":"2026-09-29T15:36:06.751174Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/agents-inc/skills/tree/main/dist/plugins/meta-planning-api-planning/skills/meta-planning-api-planning"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install agents-inc-skills@llmmart"},{"target":"git","command":"git clone https://github.com/agents-inc/skills.git"}]}