# Mvp Build Tickets

> Generate 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. Use when this capability is needed.

- Skill: `tomevault-io/mvp-build-tickets` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/mvp-build-tickets`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/mvp-build-tickets/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/mvp-build-tickets

---


# MVP Build Tickets

Create small implementation tickets in `tasks/`.

## Inputs

Read:

- `AGENTS.md`
- `agent_docs/product_requirements.md`
- `agent_docs/tech_stack.md`
- `agent_docs/page_map.md`
- `agent_docs/data_model.md`
- `agent_docs/testing.md`

## Output

Create task files such as:

```text
tasks/
  001-project-foundation.md
  002-core-layout.md
  003-data-model.md
  004-[first-core-feature].md
  005-[second-core-feature].md
  006-polish-and-launch-check.md
```

Each ticket must include:

- Goal
- Required reading
- In scope / out of scope
- Acceptance criteria
- Suggested implementation plan
- Automated and manual verification
- Risks
- Done condition

## Rules

- No ticket should say "build the app".
- Every ticket must be independently verifiable.
- Frontend tickets need browser/manual checks.
- Do not create tickets for Not-in-MVP features.

---
> Source: [kornpng/web-mvp-blueprint-kit](https://github.com/kornpng/web-mvp-blueprint-kit) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-16 -->