Vibe Code
A parent-level orchestration skill that chains Onboarding, Grill Me, Phased Plan, and Phased Implementation into one guided workflow for non-technical team members to build features safely.
Before & after
Same prompt, same agent — the only difference is the skill.
That's ambitious if you're not a developer, but it depends on how technical the feature is. You'd probably need someone technical to help with the architecture and database stuff. You might be able to handle the specifications and planning part, and then a developer could build it. It's hard to predict how long it will take without knowing the scope. What kind of feature are you thinking about? Is it part of your existing product or something new?
FEATURE BUILD WORKFLOW (non-technical co-founder → real code) PHASE 1: ONBOARDING (You + Skill) → Skill asks: What does this feature do? Who uses it? Success metric? → Skill captures your answers and your team's current tech stack → Skill builds a feature brief (written, CTO-readable) PHASE 2: GRILLING (You + Skill) → Skill asks 20 targeted questions: edge cases, error handling, data relationships → Example: "If a user deletes their account, what happens to their saved settings?" → You answer or say "not sure"; skill flags unclear items for CTO review later PHASE 3: PHASED PLAN (You + Skill) → Skill writes a 4-week plan broken into weekly PRs (never combine phases) → PR 1: Database schema + API endpoints (backend foundation) → PR 2: Frontend UI (connected to PR 1 APIs) → PR 3: Edge cases + validation logic → PR 4: Testing + documentation → Architectural questions left as "TBD (CTO review)" in the doc PHASE 4: PHASED IMPLEMENTATION (You + Skill, CTO spot-check) → Skill generates Week 1 code ready to push → You (or intern) submit PR 1; CTO reviews only the TBD items → CTO approves in 1 hour, work continues → Skill generates Weeks 2–4 sequentially (never give you everything at once) HARD GUARDRAILS (built-in) → Read-only access to production database (cannot run destructive migrations) → Skill refuses to combine multiple PRs into one (blocks your request) → All architectural questions flagged automatically (CTO unblocks, not you) → No feature ships without CTO sign-off on the TBD questions RESULT: 4-week feature, 2 CTO hours (not 40), you own the execution
About this skill
name: vibe-code description: Use when A parent-level orchestration skill that chains Onboarding, Grill Me, Phased Plan, and Phased Implementation into one guided workflow for non-technical team members to build features safely.
Vibe Code
The most opinionated skill in the set — built specifically so less-technical co-founders and interns can build real features without the CTO as a bottleneck. Vibe Code calls Onboarding, Grill Me, Phased Plan, and Phased Implementation in sequence, while enforcing hard rules: never write to production (read-only via a dedicated prod MCP), never combine multiple phases into one PR, and defer any architectural or deeply technical open questions to the CTO by leaving them unanswered in the written plan for later review.
What you get
- Full orchestrated workflow chaining 4 other skills, hard-coded production safety rules (read-only access), automatic escalation of architectural questions to a technical lead, enables non-technical contributors to ship real features safely.
Customize your output
- Adjust which questions get auto-escalated to a technical lead and customize the production-safety guardrails for your own database and MCP setup.
Example output
Non-technical co-founder used Vibe Code to build a full feature end-to-end, leaving 3 open architectural questions in the plan doc — CTO answered them via Grill Me, then work resumed without further involvement.
Best for
Technical founders and CTOs who want non-technical team members contributing real features safely, with automatic escalation of anything architecturally risky.
SKILL.md preview
---
name: vibe-code
description: Use this skill when a non-technical team member wants to build a feature end-to-end through a guided, safety-gated workflow that chains onboarding, scoping, planning, and implementation.
version: 1.0.0
category: Development / Orchestration
author: AgentVolt
license: proprietary
tags:
- development
- orchestration
- standard
---
# Vibe Code
Chains Onboarding, Grill Me, Phased Plan, and Phased Implementation into one guided path so a non-technical user can ship a real feature without a technical bottleneck, while hard safety rails stay in force.
## When to use
… (sign up to view the full skill)