$npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-build-ticketsGenerate implementation task tickets for a Web MVP. Use after AGENTS.md and agent_docs exist when the user needs small Codex-executable task files with required reading, scope, acceptance criteria, implementation plan, verification checks, risks, and done conditions.
| 1 | # MVP Build Tickets |
| 2 | |
| 3 | Create small implementation tickets in `tasks/`. |
| 4 | |
| 5 | ## Inputs |
| 6 | |
| 7 | Read: |
| 8 | |
| 9 | - `AGENTS.md` |
| 10 | - `agent_docs/product_requirements.md` |
| 11 | - `agent_docs/tech_stack.md` |
| 12 | - `agent_docs/page_map.md` |
| 13 | - `agent_docs/data_model.md` |
| 14 | - `agent_docs/testing.md` |
| 15 | |
| 16 | ## Output |
| 17 | |
| 18 | Create task files such as: |
| 19 | |
| 20 | ```text |
| 21 | tasks/ |
| 22 | 001-project-foundation.md |
| 23 | 002-core-layout.md |
| 24 | 003-data-model.md |
| 25 | 004-[first-core-feature].md |
| 26 | 005-[second-core-feature].md |
| 27 | 006-polish-and-launch-check.md |
| 28 | ``` |
| 29 | |
| 30 | Each ticket must include: |
| 31 | |
| 32 | - Goal |
| 33 | - Required reading |
| 34 | - In scope / out of scope |
| 35 | - Acceptance criteria |
| 36 | - Suggested implementation plan |
| 37 | - Automated and manual verification |
| 38 | - Risks |
| 39 | - Done condition |
| 40 | |
| 41 | ## Rules |
| 42 | |
| 43 | - No ticket should say "build the app". |
| 44 | - Every ticket must be independently verifiable. |
| 45 | - Frontend tickets need browser/manual checks. |
| 46 | - Do not create tickets for Not-in-MVP features. |