agentsclimarketplace

Prompt pack

Skill pe-menezes/vibeflow-claude/skills/prompt-pack

Generates a self-contained prompt pack from a spec. Embeds real code patterns from .vibeflow/ so any coding agent (Claude Code, Cursor, Copilot) follows the project's conventions without needing repo context. Use when handing off implementation to a separate session or agent.From its SKILL.md

Install
npx -y skills add pe-menezes/vibeflow-claude --skill prompt-pack

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.8 KB, as published. Nobody here has run it

Description and examples

What it does: Reads a spec from .vibeflow/specs/ (or path), builds a single prompt that includes objective, DoD, anti-scope, and real code patterns. Saves to .vibeflow/prompt-packs/<slug>.md. Give that file to the coding agent so it implements without needing the rest of the repo context.

Examples:

  • /vibeflow:prompt-pack .vibeflow/specs/login-flow.md — Generate prompt pack from the login-flow spec.
  • /vibeflow:prompt-pack login-flow — Same; agent finds the spec by name.

Language

Write the whole pack — opening line, objective, DoD, anti-scope, guidance — in the user's detected language. Code, paths, and technical names stay in English.

Generate a self-contained prompt pack for: $ARGUMENTS

Steps

  1. Validate spec size. Read the spec: more than 7 DoD checks, or over the budget (the spec's Budget field, else the Suggested budget line in .vibeflow/index.md, else ≤6 files), and you stop without generating the pack — tell the user it exceeds limits (N checks / N files) and to run /vibeflow:gen-spec again to split it first.
  2. Locate the spec: a file path is read directly; a feature description is matched against .vibeflow/specs/. No spec exists → generate one in the gen-spec format, save it, then continue.
  3. Read .vibeflow/conventions.md, plus the pattern docs the spec lists under Applicable Patterns. If it lists none, resolve them: read the ## Pattern Registry block in index.md (between <!-- vibeflow:patterns:start/end --> markers) and cross-reference its tags and modules against the spec's scope — top 3–5 matches; with no registry, infer which are relevant.
  4. Read the codebase files this task touches, plus anything the spec lists under References.
  5. Generate the pack.

The pack opens with

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

Then, in this order

1. Objective and Definition of Done

From the spec. Non-negotiable.

2. Anti-scope

What not to do, from the spec.

3. Budget

Max files to change — the budget resolved in step 0.

4. Project patterns to follow

What decides whether the pack works. Copy the relevant sections of .vibeflow/patterns/*.md and .vibeflow/conventions.md in full, with their real code examples — the receiving agent cannot open files you reference. Format:

## Patterns to Follow

### <Pattern Name>
<description>
<real code example from this project showing the pattern>

### Coding Conventions
<relevant conventions for this task>

5. References from the spec

Only when the spec lists References. Same self-containment rule as the patterns: embed the mockup, the test file, or the snippet the implementation has to match, in full. Too large to embed → give the verified path and say what the agent should take from it. A reference that is neither embedded nor reachable by the receiving agent doesn't belong in the pack.

6. Where to work

Real file paths from the codebase, with the code snippets that give them context.

7. Directional guidance

Architectural direction and constraints to respect, not step-by-step instructions. The pack carries this contract, adapted to the task:

Deliver what the spec asks, at the scope it defines. Make routine judgment calls yourself; check in only when different readings would lead to materially different work. If the spec seems mistaken, say so in a sentence and continue as specified. Finish the whole task, and stop short of changes clearly beyond it. Match what you write — code, docs, comments — to what the task needs, without filler or boilerplate.

8. How to run and test

Required. Detect the runner from .vibeflow/index.md or the project's config files and include the command, plus any the spec lists. None detected → "No test runner detected. Add manual tests to validate." Format:

## How to validate
1. Run tests: <detected command>
2. Verify manually: [description]

9. Docs to update

Which docs need changes after implementation.

Flag any path you could not verify with <!-- TODO: verify this path -->.

Save the prompt pack to .vibeflow/prompt-packs/<feature-slug>.md (create the directory if it doesn't exist).

After saving, suggest: "Prompt pack saved. Hand it off to the coding agent. After implementation, run /vibeflow:audit with the spec to verify."


Maintenance

If this command is modified, update MANUAL.md to reflect the changes.

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.