prompt-pack

Decomposes large changes into sequenced, self-contained prompts executed across fresh chat sessions.

83|8|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/nelsonwerd/idea-to-ship-skills --skill prompt-pack-nelsonwerd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompt-pack
Source: https://github.com/nelsonwerd/idea-to-ship-skills/tree/main/skills/prompt-pack
Command: npx skills add https://github.com/nelsonwerd/idea-to-ship-skills --skill prompt-pack-nelsonwerd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large or risky code changes often die to context/token limits, lose their plan between sessions, or ship half-broken when one chat tries to do everything. This Skill turns a big job into an ordered pack of small, self-contained prompts — each run in its own fresh chat, each leaving the project in a working, verifiable state — so work survives context limits and relays cleanly across chats and tools. ## Core Features & Use Cases - Pack authoring (Mode A): Performs read-only architecture reconnaissance and a pre-flight constraint scan, locks decisions and scope fences, then decomposes the work into risk-rated prompts with guardrails, verification matrices, and commit messages, saved to docs/<TOPIC>_PROMPT_PACK.md. - Pack execution (Mode B): Runs exactly one pack prompt per chat with a read-first protocol, file:line verification against current code, strict scope guardrails, and a report-and-stop loop that never commits without explicit approval. - Handoff briefings (Mode C): Writes paste-ready, self-contained briefings to resume a dying chat or relay work to another tool such as Codex via AGENTS.md. - Use Case: You need to migrate a backend across many files but keep running out of context. Ask for a prompt pack, receive a sequenced P1→P8 plan, then paste each prompt into a fresh chat, verify, commit, and continue until the migration ships. ## Quick Start Ask the AI to make a prompt pack for your large change, for example: "Break this onboarding rebuild into a prompt pack I can run one prompt per fresh chat."

Frequently Asked Questions about prompt-pack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a large code change into prompts for separate chats?▼

Ask for a prompt pack: the Skill reads your codebase, maps the architecture, and writes a sequenced file of self-contained prompts to docs/. Each prompt is pasted into its own fresh chat, verified, committed, and followed by the next.

How do I continue work when my chat is running out of context?▼

Request a handoff briefing (Mode C). The Skill writes a paste-ready message capturing shipped work, current tree state, landmines, and the exact next step, so a fresh chat or another tool resumes with full context.

Can I hand off prompts from Claude to Codex or another tool?▼

Yes. Prompts are written to be fully self-contained, restating rules inline and referencing AGENTS.md where relevant, so they can be pasted into another agent with no loss of context. Multi-unit relays become a full pack.

When should I not use a prompt pack?▼

Skip it for small changes that fit comfortably in one chat, one-line fixes, quick questions, or pure research with no shippable units. Also validate unsettled product ideas first rather than sequencing an unvalidated concept.

What happens if the code has changed since the pack was written?▼

Executing prompts verify every file:line reference against current code before editing and push back on mismatches. If drift is structural enough to invalidate later prompts, execution stops and flags the pack for re-planning.