Feature Specification
owainlewis/blueprint
Writes one implementation-ready spec for a feature or major change, settling behavior, technical design, failure handling and acceptance checks before delivery.
Writes an MVP technical design from agreed requirements, covering architecture, data ownership, integration contracts, deployment and tradeoffs, then hands off to the next stage.
Install MVP Technical Design
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install KhazP/vibe-coding-prompt-template vibe-techdesign --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vibe-techdesign .claude/skills/vibe-techdesign && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibe-techdesign" agent skill from https://github.com/KhazP/vibe-coding-prompt-template/tree/main/.agents/skills/vibe-techdesign into .claude/skills/vibe-techdesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-techdesign", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/KhazP/vibe-coding-prompt-template/tree/main/.agents/skills/vibe-techdesignType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install KhazP/vibe-coding-prompt-template vibe-techdesign --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/vibe-techdesign .agents/skills/vibe-techdesign && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-techdesign" agent skill from https://github.com/KhazP/vibe-coding-prompt-template/tree/main/.agents/skills/vibe-techdesign into .agents/skills/vibe-techdesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-techdesign", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install KhazP/vibe-coding-prompt-template vibe-techdesign --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/vibe-techdesign .cursor/skills/vibe-techdesign && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-techdesign" agent skill from https://github.com/KhazP/vibe-coding-prompt-template/tree/main/.agents/skills/vibe-techdesign into .cursor/skills/vibe-techdesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-techdesign", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/KhazP/vibe-coding-prompt-template.git --path .agents/skills/vibe-techdesign--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install KhazP/vibe-coding-prompt-template vibe-techdesign --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/vibe-techdesign .gemini/skills/vibe-techdesign && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibe-techdesign" agent skill from https://github.com/KhazP/vibe-coding-prompt-template/tree/main/.agents/skills/vibe-techdesign into .gemini/skills/vibe-techdesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-techdesign", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install KhazP/vibe-coding-prompt-template vibe-techdesignInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/vibe-techdesign .github/skills/vibe-techdesign && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibe-techdesign" agent skill from https://github.com/KhazP/vibe-coding-prompt-template/tree/main/.agents/skills/vibe-techdesign into .github/skills/vibe-techdesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-techdesign", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install KhazP/vibe-coding-prompt-template vibe-techdesign --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/vibe-techdesign .opencode/skills/vibe-techdesign && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-techdesign" agent skill from https://github.com/KhazP/vibe-coding-prompt-template/tree/main/.agents/skills/vibe-techdesign into .opencode/skills/vibe-techdesign/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-techdesign", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibe-techdesign- GitHub stars
- 3.1k
- Token cost
- ~512 tokens
- SKILL.md length
- 237 words
- Files
- 3 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes an MVP technical design from agreed requirements, covering architecture, data ownership, integration contracts, deployment and tradeoffs, then hands off to the next stage.
- Turning agreed requirements into an MVP architecture and implementation plan
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Choosing between simple and heavier infrastructure for a first release
- Writing a tech design document that the next workflow stage can consume
What it does
The skill reads the agreed requirements and any handoff context, inspects the stack and relevant code of an existing project before proposing replacements, and asks only about consequential choices that are still open. It describes the architecture for the core journey: component or service boundaries, data ownership, integration contracts, deployment target and failure behavior. It prefers the smallest design that meets the requirements and adds auth, storage, infrastructure, AI or paid services only when justified.
The design records tradeoffs, compatibility constraints, migration or recovery needs and how the result will be checked, separates local test operations from external sends, production writes and deployments, and keeps secrets out of the document. Output goes to the manifest's configured path or a TechDesign file under docs. Quick mode can be a short plan, and deeper modes expand only where risk warrants. It ends with handoff context (app, user level, platform, budget, timeline, constraints, decisions, open questions), and for the vibeworkflow tool it includes the exact CLI output metadata from a reference file.
When your agent uses it
- Turning agreed requirements into an MVP architecture and implementation plan
- Choosing between simple and heavier infrastructure for a first release
- Writing a tech design document that the next workflow stage can consume
Example prompts
- “Write the MVP tech design for the recipe-sharing app from the PRD in docs/.”
- “Propose the smallest architecture for this booking tool and note the tradeoffs.”
- “Review my existing Next.js project and draft a technical design for adding payments.”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Glob, Grep, WebSearch, AskUserQuestion
What it can do on your machine
Read from SKILL.md and the folder at commit d26fb0d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteGlobGrepWebSearchAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
MVP Technical Design loads about 512 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 237 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from KhazP/vibe-coding-prompt-template at commit d26fb0d, republished under its MIT licence (© KhazP). 237 words, ~512 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-techdesign/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- vibe-techdesign
- description
- Write an MVP technical design from agreed requirements, including architecture choices and relevant tradeoffs.
- allowed-tools
- Read, Write, Glob, Grep, WebSearch, AskUserQuestion
MVP technical design
Read the agreed requirements and reuse Handoff Context. Inspect an existing project's stack and relevant implementation before proposing replacements. Ask only for consequential choices that remain unresolved; a known answer does not need another confirmation echo.
Describe the architecture needed for the core journey: component/service boundaries, data ownership, integration contracts, deployment target, and relevant failure behavior. Prefer the smallest design that meets requirements. Add auth, storage, infrastructure, AI, or paid services only when justified. Verify changing vendor details from the installed code or official sources.
Record meaningful tradeoffs, compatibility constraints, migration/recovery requirements where applicable, and how the result will be checked. Distinguish local test operations from external sends, production writes, and deployments. Keep secrets out of generated documents. Do not assign broad tool permissions or require a team of agents to execute an ordinary implementation.
Use the manifest's configured design path or docs/TechDesign-[AppName]-MVP.md.
Quick mode can be a short architecture and implementation plan; deeper modes
should expand only where uncertainty or risk warrants it. End with Handoff
Context carrying app, known user level, platform, budget, timeline, mode,
constraints, decisions, source files, and open questions. Continue to the next
authorized workflow stage rather than stopping solely because a document exists.
For a guided interview with unresolved requirements, consult the relevant optional question prompts.
When producing a document for vibeworkflow, include the exact
CLI output metadata. This is a parser contract,
not an optional prose template.
© KhazP, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .agents/skills/vibe-techdesign of KhazP/vibe-coding-prompt-template.
- SKILL.md
- references/cli-output.md
- references/question-bank.md
Open the folder on GitHubat commit d26fb0d
Compare with similar skills
MVP Technical Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| MVP Technical Design this skillKhazP/vibe-coding-prompt-template | 3.1k | — | ~512 | Automated safety check: Pass | MIT | |
| Feature Specificationowainlewis/blueprint | 412 | — | ~938 | Automated safety check: Pass | MIT | |
| BiSheng SDD Document Reviewdataelement/bisheng | 12k | — | ~717 | Automated safety check: Pass | Apache-2.0 | |
| Dark Architecture Diagram BuilderCocoon-AI/architecture-diagram-generator | 7.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Deepwiki Rssopaco/deepwiki-rs | 3.1k | — | ~748 | Automated safety check: Pass | MIT | |
| Mermaid Diagramsjjmartres/opencode | 133 | 6 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
BiSheng SDD Document Review
dataelement/bisheng
Reviews BiSheng spec, design and tasks documents with checklists for PRD gaps, handover readiness and acceptance traceability, producing a report or an LGTM.
Dark Architecture Diagram Builder
Cocoon-AI/architecture-diagram-generator
Creates dark-themed system, cloud, security and network architecture diagrams as self-contained HTML files with inline SVG and CSS.
Deepwiki Rs
sopaco/deepwiki-rs
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation.
Mermaid Diagrams
jjmartres/opencode
Helps an agent pick the right Mermaid diagram type and write the syntax for class, sequence, flow, ER, C4, state and other software diagrams.
Ontology-Driven System Builder
sharptoolbox/ontology-driven-dev
Runs a three-step pipeline, requirement exploration, seven-model ontology YAML, then app build, on a Flask, SQLite, and React stack with sign-off gates.
More from KhazP/vibe-coding-prompt-template
All 11 skills in this repoMVP Product Requirements Writer
KhazP/vibe-coding-prompt-template
Writes or revises an MVP product requirements document, sized to the product, with observable acceptance criteria and no repeated questions.
Vibe Research
KhazP/vibe-coding-prompt-template
Researches an app idea or settles product and technical uncertainties before a design is fixed, and saves the findings with a handoff for the next stage.
Vibe Debug
KhazP/vibe-coding-prompt-template
A short debugging procedure for an existing project: reproduce the failure, test one hypothesis at a time, make the smallest fix, add a regression check and re-verify.
Vibe Workflow Router
KhazP/vibe-coding-prompt-template
Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.
Vibe Agents Instructions
KhazP/vibe-coding-prompt-template
Writes project agent instructions and tool setup from decided requirements and the existing repo, keeping only stable, non-obvious guidance in always-loaded files.
Build a New-Project Slice
KhazP/vibe-coding-prompt-template
Builds one working slice of a new project from the brief, runs the affected checks and the user journey, and reports what was and was not verified.
Related
Categories
Questions about MVP Technical Design
What does MVP Technical Design do?
Writes an MVP technical design from agreed requirements, covering architecture, data ownership, integration contracts, deployment and tradeoffs, then hands off to the next stage. The skill reads the agreed requirements and any handoff context, inspects the stack and relevant code of an existing project before proposing replacements, and asks only about consequential choices that are still open. It describes the architecture for the core journey: component or service boundaries, data ownership, integration contracts, deployment target and failure behavior.
When should I use MVP Technical Design?
MVP Technical Design fits situations like: turning agreed requirements into an MVP architecture and implementation plan; choosing between simple and heavier infrastructure for a first release; writing a tech design document that the next workflow stage can consume.
How do I install MVP Technical Design in Claude Code?
Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a claude-code`. Or copy the skill folder (.agents/skills/vibe-techdesign in KhazP/vibe-coding-prompt-template) into .claude/skills/vibe-techdesign in your project. Claude Code loads it when a task matches its description.
How do I install MVP Technical Design in Codex?
Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a codex`. Or copy the skill folder (.agents/skills/vibe-techdesign in KhazP/vibe-coding-prompt-template) into .agents/skills/vibe-techdesign in your project. Codex loads it when a task matches its description.
Can I use MVP Technical Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-techdesign, .gemini/skills/vibe-techdesign, .github/skills/vibe-techdesign and .opencode/skills/vibe-techdesign in your project.
What does MVP Technical Design need to run?
SKILL.md names no scripts, command-line tools or credentials: MVP Technical Design is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Glob, Grep, WebSearch, AskUserQuestion.
Does MVP Technical Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is MVP Technical Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does MVP Technical Design use?
MVP Technical Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does MVP Technical Design use?
About 512 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.
What are the alternatives to MVP Technical Design?
Skills that share tags, products or a category with MVP Technical Design: Feature Specification (owainlewis/blueprint, 412 stars), BiSheng SDD Document Review (dataelement/bisheng, 12k stars), Dark Architecture Diagram Builder (Cocoon-AI/architecture-diagram-generator, 7.4k stars) and Deepwiki Rs (sopaco/deepwiki-rs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains MVP Technical Design?
KhazP (a GitHub user) maintains it in KhazP/vibe-coding-prompt-template, which has 3,130 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 4, 2026.
Source: KhazP/vibe-coding-prompt-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.