Vibe Coding Roadmap by Pooya Hayati
Vibe Coding Skill
A risk-adaptive engineering Head for AI-assisted development of small, medium and large software projects, including WordPress plugins. Works with OpenAI Codex, Claude Code and compatible skill-based agents.
Current version: 1.9.0 — stable release and portable ZIP.
One engineering Head, focused specialists
Vibe is the project manager and senior engineer: it owns scope, stack, architecture, risk, approvals, test selection, integration and final acceptance. Specialists supply domain methods and evidence; the Head retains shared engineering controls and accepts their results.
Prefer existing platform capabilities and suitable extensions before custom code. Keep a working stack unless requirements justify changing it; choose technology from product needs, not project size alone.
Before adding a subsystem, dependency or service, inspect the existing alternative and record the concrete need and maintenance cost in the existing decision note. Small fixes need no architecture exercise.
Development workflow
Head: Vibe owns the work. Both: the specialist supplies domain work and Vibe coordinates/accepts it. Supporting: scoped advice or evidence. Every stage remains Head-controlled.
| Stage | What happens | Who does it | When it applies |
|---|---|---|---|
| 1 · Discover | Inspect rules, affected code, boundaries and risk; route capabilities. | Head; Supporting: debugging, necessary UI assessment, Graphify. | New objective or changed scope/impact evidence. |
| 2 · Define | State the outcome, scope, protected behavior and acceptance criteria. | Head; Supporting: UI flows, security boundaries, API obligations. | Material requirements remain unclear; reuse settled decisions. |
| 3 · Plan | Choose approach, installation target, ownership, sequence and checks; preflight Trivy for publication. | Head; relevant specialists Supporting. | New product/startup decisions; a written plan for high-risk or cross-boundary work. |
| 4 · Design | Resolve changed UI, API and security decisions. | Both: selected specialists design their domains; Head owns architecture/integration. | Changed interfaces or trust boundaries need design. |
| 5 · Build | Implement and integrate small runnable slices and selected packaging. | Head; Both on assigned domain surfaces; debugging Supporting. | Scope and necessary design decisions are ready. |
| 6 · Verify | Check outcomes, relevant failures and selected installation behavior. | Head selects checks; Both for domain evidence; Trivy Supporting. | Relevant behavior changes; reuse sufficient existing evidence. |
| 7 · Review | Assess the diff, findings, compatibility and evidence sufficiency. | Head owns readiness; domain review Supporting. | Before meaningful integration or merge. |
| 8 · Ship | Deliver the authorized artifact/release/deployment and verify its state; require native Trivy scans before publication. | Head; retained evidence and delivery debugging Supporting. | Delivery is authorized and required gates pass. |
These are responsibilities, not eight mandatory documents or approvals. Small tasks combine stages; larger work iterates vertical slices. Failed checks return to the affected decision. Canonical lifecycle and exit conditions.
Project size and risk tiers
Project complexity, task risk and affected scope are separate decisions. A payment change in a small plugin can be critical; a label correction in a large app can stay lightweight.
| Project size | Typical shape | Delivery route |
|---|---|---|
| Small | Focused site, utility or plugin with few components. | Simplest adequate stack, short runnable steps, focused checks. |
| Medium | Multiple features, modules or integrations. | Clear boundaries, vertical slices, affected contract/integration checks. |
| Large | Multiple domains, teams, services or data/operational boundaries. | Decompose, confirm ownership/contracts, map consequential impact and integrate verifiable slices. |
| Task tier | Typical change | Required depth |
|---|---|---|
| 0 · Tiny | Local, reversible copy/visual change without security/data effects. | Understand, change and focused check; usually no new automated test. |
| 1 · Standard | Bounded feature. | Acceptance, impact, implementation, relevant tests and review. |
| 2 · Significant | Auth, migrations, integrations, shared contracts or meaningful dependencies. | Explicit spec/plan, impact analysis and stronger relevant security/regression checks. |
| 3 · Critical | Destructive/irreversible work, sensitive data or material production impact. | Tier 2 controls, required approval, recovery plan and strong evidence; stop if critical verification is missing. |
WordPress work additionally preserves public APIs, authorization, lifecycle/data retention, affected WooCommerce compatibility and the exact installable ZIP. Operating model · Risk rules.
Registered specialists
| Specialist | Purpose and trigger | Main stages |
|---|---|---|
| UI-UX-Skill | Sole UI/UX specialist: websites, apps, dashboards and WordPress interfaces, including responsive/RTL, accessibility and rendered validation. | Design · Build · Verify · Review |
| Security and hardening | Auth/access, sensitive data, uploads, payments and external trust boundaries. | Design · Build · Verify · Review |
| API and interface design | Producer/consumer contracts, errors, compatibility, retries and idempotency. | Design · Build · Verify · Review |
| Debugging and error recovery | Unclear/intermittent failures, repeated failed fixes and delivery failures. | Discover · Build · Verify · Ship on failure |
Use specialists only for matching work; never install the entire external collection. Check currency and instruction compatibility. Reviewed mechanical edits reuse accepted guidance; material domain decisions use a bounded assignment and separate Head acceptance of the result. Retained commitments still apply. Composition and freshness.
| Role | Responsibility | Boundary |
|---|---|---|
| Vibe Head | Engineering decisions, integration, acceptance and authorized delivery. | System/developer/user instructions, project rules and host permissions remain authoritative. |
| Specialist | Assigned domain decisions, authorized edits, relevant checks and findings. | Cannot independently expand scope, change architecture, install arbitrary dependencies, start agents or publish. |
| Tool | Requested graph/scan evidence. | Grants no permissions or final engineering authority. |
Head precedence cannot dismiss a real vulnerability or contradictory evidence. These are instruction boundaries, not an OS sandbox. Authority contract.
Supporting tools
| Tool | Purpose | When used | Limits |
|---|---|---|---|
| Context7 | Relevant library/API documentation matched to the project's actual supported version. | Plan/Build for unfamiliar or version-sensitive APIs, configuration and migrations; reuse settled evidence. | Optional provider; official versioned/local docs are the fallback. No automatic host installation, paid plan or lookup for every edit. Usage and privacy. |
| Graphify | Code relationships and consequential impact analysis. | Discover/Plan and targeted Review for unfamiliar or cross-module work. | Confirm relationships in source/runtime; use source analysis if unavailable. Semantic processing needs its own authorization. |
| Trivy | Local secret and relevant dependency/configuration scans. | Publication planning: check native availability. Verify/Review: assess findings. Ship: scan the final artifact before publication. | Missing/failed/incomplete scans block publication; a clean scan does not prove application logic or authorization. |
Keep generated reports outside product source. Development uses native project controls; Trivy is the only additional scanner in the Head workflow. Native release gate.
Verification and delivery
-
Changed acceptance checks need review against their pre-change definitions; a new green result cannot silently excuse deleted assertions or weaker expectations. Relevant security outcomes retain denial/data-protection evidence across handoffs. These controls add no blanket test quota.
-
Capacity, performance and recovery claims need evidence under stated workload/environment conditions. Local Docker/Compose startup alone is not proof of production scalability; ordinary edits do not trigger load tests. Operational evidence.
-
Define an observable outcome and preserve approved scope, business rules and platform invariants. Use focused checks during implementation, relevant integration checks before merging, and artifact/security checks for publication. Reuse valid evidence; no fixed test-count, evidence-family or coverage quota. Required project checks still apply. Verification policy.
-
Preserve acceptance criteria, required checks and unresolved findings across handoffs and resumes. For structured tasks, validate recorded results against the relevant code and artifacts. A successful command alone does not prove the intended outcome. Completion and trust limits.
-
Deliver what works, how to start/use it, actual checks, unresolved limits and the next action. Merge, release, deployment and local installation are distinct outcomes.
Choose the simplest reproducible startup path. When useful or requested, suitable self-hosted apps can offer local Docker Compose installation, checked through clean startup, a core workflow and required data persistence. WordPress plugins still need an installable ZIP; desktop/mobile products need their appropriate native packages. Product installation and runtime checks.
Requirements, updates and feedback
Python 3.10+ and Git are required for the Skill's helper scripts; network access is needed to check current upstream versions and dependency information. Tool requirements depend on the task, as described above. Installation and prerequisites.
Check the Head and selected specialists against the latest stable release, using the default branch only when no stable release exists. Preserve local edits and keep instructions stable during an assignment. Install/update only within existing authorization. Daily specialist checks run during active preflights; idle checks require a host scheduler. Update and freshness policy.
For a suspected defect in Vibe itself, prepare a minimal English local report with attribution and evidence. After removing sensitive details, the user may email it to hayatipooya@gmail.com; nothing is sent automatically. Feedback route.
Documentation
- Install and verify · Version updates · Technical changelog
- Current status and roadmap · Implementation and acceptance index
- Skill instructions · Lifecycle and architecture · Context and planning
- Specialist composition · Authority · Shared formats and migration
- Verification · WordPress delivery · Security reporting
- Contributor checks · Maintainer validation and evidence limits
License
Author
Created and maintained by PooyaHayati | پویا حیاتی.
Website: https://Pooyahayati.com