version: "1.0.2" name: Vibecode Execution Templates description: Sidecar data for /vibecode workflow — verification checklists, exit criteria templates, and report formats loaded just-in-time. trigger: /vibecode workflow execution glob: source: user

Skill: Vibecode Execution Templates

Sidecar Skill for the /vibecode workflow. Contains execution templates,

verification checklists, and report formats that the Agent loads **only when

executing a specific mode**.

Pattern: Workflow = Logic → Sidecar Skill = Data Router.

The /vibecode workflow instructs the Agent to read this skill at mode-start time.

When to Load

References

Mode Chaining Guide

Recommended chains:
 
  New plan:     review → loop --sandbox → apply → auto
  Quick fix:    loop (standalone, real project)
  Risky phase:  review → loop --sandbox [Phase N] → apply → auto --resume
  Quick peek:   loop --sandbox --max 1 (one-shot preview)
  Full dry-run: auto --sandbox (entire plan in sandbox)
  Free session: session (DSP draft → JIT phases → Quality Gate → commit)
  Targeted:     session refactor-auth (DSP with topic → Phase 1 ready)
  Hardened:     session --hardened (auto-detect + forced TDD on sensitive code)

Scope Expansion Guard (Dynamic Task Addition)

During a vibecode session (especially in loop or auto mode), if the Agent discovers a missing requirement or edge case and creates a new ad-hoc task, it MUST:

1. Check if the current session or active plan enforces CSA or TDD (by reading .para-workspace.yml, project.md, or active memory).
2. If CSA/TDD is active, the Agent MUST HALT and ask the user: "This new task requires a Spec update (CSA) and/or Test Case (TDD). Shall I propose the spec/test changes first?"
3. Only after the Spec/Test is updated and approved (or if the user explicitly overrides), may the Agent proceed to implement the production code.

Phase Context Reload (Session Mode)

At the start of every Phase in session mode, Agent MUST reload context to prevent drift in long sessions. This table defines WHAT to reload.

Mandatory (EVERY Phase)

Conditional (based on activated Quality Tools)

Pattern: The /vibecode workflow references this table at Step 2a (Context Reload).

Agent reads the sidecar skill → follows the routing table → loads the right skills.

This keeps the workflow file lean and the routing logic centralized here.

Output Checklist

After execution, verify:

• [ ] Step 0 Pre-flight executed (rules + skills reloaded)
• [ ] Correct mode was used for the target task complexity
• [ ] All exit criteria explicitly defined (loop mode)
• [ ] User confirmed before real writes
• [ ] Phase gates respected (auto mode)
• [ ] Quality Gate and Pre-Code Checkpoint presented at EVERY Phase start (session mode — TDD/graph/QA/hardened)
• [ ] Phase Start Baseline Gate presented at EVERY Phase ≥ 1 (proposing /brainstorm, /qa, /spec, /research)
• [ ] Post-Baseline Approval Gate enforced: Agent STOPPED turn after brainstorm/spec/qa output and waited for user confirmation before coding (Guard #17)
• [ ] User approval obtained at Pre-Code Checkpoint and confirmed to run /plan [project-name] dev before making any code modifications
• [ ] Rollback mechanism available (loop: git stash, sandbox: delete)
• [ ] Path substitution correct (--sandbox: sandbox prefix)
• [ ] Bash scripts syntax-checked with bash -n (--sandbox)
• [ ] Sandbox cleaned up after completion
• [ ] Final report generated with file inventory + lessons learned
• [ ] Pre-git Task Done Check (check-phase-tasks.js) executed with exit code 0 before every git commit
• [ ] Mandatory User confirmation obtained (suggesting /plan [project-name] end) before performing session teardown or archiving/cleaning plan files