mvp-workflow

Name: mvp-workflow
Author: kornpng

29stars0forks

How to install mvp-workflow?

kornpng/web-mvp-blueprint-kit/mvp-workflow

$npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-workflow

Installs into the current project.

Summary

Orchestrate a Codex-first Web MVP planning workflow from rough idea to build-ready artifacts. Use when the user wants to turn an app idea into a structured MVP plan, PRD, technical blueprint, AGENTS.md context, and implementation tickets.

Files · 1

View on GitHub

SKILL.md

1	# MVP Workflow
2
3	Guide the user through the full Web MVP Blueprint workflow.
4
5	## Workflow
6
7	1. Idea Brief - clarify the first user, problem, smallest useful outcome, and MVP boundary.
8	2. Evidence Research - collect competitor, user, pricing, and feasibility evidence.
9	3. Buildable PRD - define pages, features, data objects, acceptance criteria, and success metrics.
10	4. Technical Blueprint - choose a practical stack and implementation route.
11	5. Agent Context - generate `AGENTS.md` and `agent_docs/`.
12	6. Build Tickets - generate task files that Codex can execute one at a time.
13
14	## State Check
15
16	Inspect the current project before choosing the next step:
17
18	\| Artifact \| Meaning \|
19	\|---\|---\|
20	\| `docs/IdeaBrief-*.md` \| Step 0 complete \|
21	\| `docs/EvidencePack-*.md` \| Step 1 complete \|
22	\| `docs/BuildablePRD-*.md` \| Step 2 complete \|
23	\| `docs/TechBlueprint-*.md` \| Step 3 complete \|
24	\| `AGENTS.md` and `agent_docs/` \| Step 4 complete \|
25	\| `tasks/*.md` \| Step 5 complete \|
26
27	## Routing
28
29	- If no idea brief exists, use `$mvp-idea-brief`.
30	- If idea brief exists but no evidence pack exists, use `$mvp-research`.
31	- If evidence exists but no buildable PRD exists, use `$mvp-prd`.
32	- If PRD exists but no technical blueprint exists, use `$mvp-tech-design`.
33	- If technical blueprint exists but no agent context exists, use `$mvp-agent-context`.
34	- If agent context exists but no task tickets exist, use `$mvp-build-tickets`.
35
36	## Rules
37
38	- Keep the user oriented with the current step and next artifact.
39	- Ask one question at a time when inputs are missing.
40	- Favor small Web MVP scope over broad product ambition.
41	- Preserve explicit "Not in MVP" decisions.
42	- Do not start implementation until agent context and tickets exist, unless the user explicitly skips planning.

People who liked this also viewed

6 picks

Type

mvp-workflow

29stars0forks

View on GitHub

How to install mvp-workflow?

kornpng/web-mvp-blueprint-kit/mvp-workflow

$npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-workflow

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# MVP Workflow
2
3	Guide the user through the full Web MVP Blueprint workflow.
4
5	## Workflow
6
7	1. Idea Brief - clarify the first user, problem, smallest useful outcome, and MVP boundary.
8	2. Evidence Research - collect competitor, user, pricing, and feasibility evidence.
9	3. Buildable PRD - define pages, features, data objects, acceptance criteria, and success metrics.
10	4. Technical Blueprint - choose a practical stack and implementation route.
11	5. Agent Context - generate `AGENTS.md` and `agent_docs/`.
12	6. Build Tickets - generate task files that Codex can execute one at a time.
13
14	## State Check
15
16	Inspect the current project before choosing the next step:
17
18	\| Artifact \| Meaning \|
19	\|---\|---\|
20	\| `docs/IdeaBrief-*.md` \| Step 0 complete \|
21	\| `docs/EvidencePack-*.md` \| Step 1 complete \|
22	\| `docs/BuildablePRD-*.md` \| Step 2 complete \|
23	\| `docs/TechBlueprint-*.md` \| Step 3 complete \|
24	\| `AGENTS.md` and `agent_docs/` \| Step 4 complete \|
25	\| `tasks/*.md` \| Step 5 complete \|
26
27	## Routing
28
29	- If no idea brief exists, use `$mvp-idea-brief`.
30	- If idea brief exists but no evidence pack exists, use `$mvp-research`.
31	- If evidence exists but no buildable PRD exists, use `$mvp-prd`.
32	- If PRD exists but no technical blueprint exists, use `$mvp-tech-design`.
33	- If technical blueprint exists but no agent context exists, use `$mvp-agent-context`.
34	- If agent context exists but no task tickets exist, use `$mvp-build-tickets`.
35
36	## Rules
37
38	- Keep the user oriented with the current step and next artifact.
39	- Ask one question at a time when inputs are missing.
40	- Favor small Web MVP scope over broad product ambition.
41	- Preserve explicit "Not in MVP" decisions.
42	- Do not start implementation until agent context and tickets exist, unless the user explicitly skips planning.

People who liked this also viewed

6 picks

Type