القائمة
Use when explicitly defining MVP scope, exclusions, beta screens, states, or success metrics.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when writing or updating an ADR for a specific technical decision.
Use when creating, reviewing, or restructuring AGENTS.md, CLAUDE.md, or scoped instruction files for a project, including root, feature, service, backend, or domain-level guidance.
Use when a new app plan already exists and needs an interactive kickoff into setup decisions and first tasks.
Use at task handoff, milestone review, or after implementation when project lessons may be reusable for future apps, toolkit docs, AGENTS/CLAUDE instructions, skills, or templates.
Use when a greenfield app needs a mature foundation plan before implementation.
Use when drafting pull request descriptions, end-of-session handoffs, reviewer notes, verification summaries, or stop-start task updates.
| name | mvp-boundary-mapper |
| description | Use when explicitly defining MVP scope, exclusions, beta screens, states, or success metrics. |
Use this skill to turn product ideas into a focused first build.
references/mvp-boundary-and-screen-map.md; fall back to docs/foundation/mvp-boundary-and-screen-map.md when installed.The MVP should prove user understanding and trust before broad automation, monetization, or admin tooling.