Vibeflow Prompt Pack.prompt

---
name: 'vibeflow-prompt-pack'
description: 'Generates a self-contained prompt pack from a spec with embedded patterns for any coding agent.'
agent: 'vibeflow-architect'
---

# Vibeflow: Prompt Pack

> format-agnostic, repo-local prompt asset

Generate a self-contained prompt pack from a spec. The prompt pack
is designed for a coding agent (Copilot, Cursor, Claude Code, etc.) that
has NO context beyond the prompt itself. Embeds real patterns from
`.vibeflow/` so the agent follows the project's conventions.

**Usage:** Provide the spec file path or feature name as input.

---

## Language

The prompt pack MUST be written in the user's detected language.
The opening line should be language-adaptive:
Write the opening line in the user's detected language. The concept is:
"You are only seeing this prompt; there is no context outside it."

All textual content (objective, DoD, anti-scope, guidance) should be in
the detected language. Code, paths and technical names remain in English.

## Steps:

0. **Validate spec size.** Read the spec and check:
   - If it has **>7 DoD checks**, OR
   - If it exceeds the **budget** (from `.vibeflow/index.md` or default ≤ 6 files)

   If EITHER condition is true, **stop**. Do NOT generate the prompt pack.
   Instead, inform the user: "This spec exceeds limits (N DoD checks / N files).
   Run vibeflow-gen-spec again to split it into smaller specs before generating
   a prompt pack."

1. If the input is a file path, read that spec file.
2. If it's a feature description, look for a matching spec in `.vibeflow/specs/`.
3. If no spec exists, generate one first (following gen-spec format), save it,
   then continue.
4. Read `.vibeflow/` docs:
   - `.vibeflow/conventions.md` (always)
   - Pattern docs listed in the spec's "Applicable Patterns" section (manual override)
   - If the spec doesn't list patterns: **use Pattern Resolution.** Read the
     `## Pattern Registry` YAML block from `index.md` (between
     `<!-- vibeflow:patterns:start/end -->` markers). Cross-reference the
     registry's tags and modules against the spec's scope. Load the top 3-5
     matching patterns. If no registry exists, infer which ones are relevant.
5. Read the actual codebase files relevant to this task.
6. Generate the prompt pack.

## The Prompt Pack MUST Start With:

> You are only seeing this prompt; there is no context outside it.

(Write this opening line in the user's detected language.)

## Then include, in this order:

### 1. Objective and Definition of Done
Copied from the spec. Non-negotiable.

### 2. Anti-scope
What NOT to do. Copied from spec.

### 3. Budget
Max files to change. Read the budget from the spec. If the spec doesn't
specify a budget, check `.vibeflow/index.md` for the `Suggested budget`
line. If neither is available, default to ≤ 6.

### 4. Project Patterns to Follow
THIS IS CRITICAL. Embed the actual patterns the agent must follow.
Copy the relevant sections from `.vibeflow/patterns/*.md` and
`.vibeflow/conventions.md` directly into the prompt pack.

Include REAL code examples from the pattern docs — not references to
external files the agent won't see. The prompt pack is self-contained.

Format as: