prompt-chain

Generates self-contained prompts that carry context and authority across isolated chat sessions.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/1marcelserrano/prompt-chain --skill prompt-chain-1marcelserrano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-chain
Source: https://github.com/1marcelserrano/prompt-chain/tree/main/skills/prompt-chain
Command: npx skills add https://github.com/1marcelserrano/prompt-chain --skill prompt-chain-1marcelserrano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step work breaks down when it must span multiple chat sessions: context is lost, decisions get re-litigated, and authority boundaries blur. This Skill turns a complex task into self-contained, cold-start prompts that carry the full work frame, decisions, and permissions into every fresh chat. ## Core Features & Use Cases - CHAIN mode: Decomposes sequential work into 2-6 stages where each stage executes its slice and emits the next stage's prompt with updated context, ending in a CHAIN COMPLETE report. - FAN-OUT mode: Generates one independent prompt per piece of work sharing identical stable context, with optional dispatcher and collector prompts for combined results. - Authority-safe propagation: Keeps operator decisions, observed facts, and stage proposals labeled separately so no stage silently widens permissions or promotes a proposal into a decision. - Use Case: You need to refactor a stylesheet and then validate responsive behavior in separate clean chats. The Skill produces a Stage 1 prompt you paste into a new chat; that chat does the refactor and emits the Stage 2 validation prompt automatically. ## Quick Start Ask the agent to break your multi-step task into a prompt chain where each stage runs in a fresh chat and generates the next stage's prompt.

Frequently Asked Questions about prompt-chain

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

FAQPage Schema
How do I split a large task across multiple chat sessions?

Use CHAIN mode for sequential work: the Skill writes a Stage 1 prompt you paste into a fresh chat, and each completed stage emits the next stage's prompt with updated context. For independent pieces, FAN-OUT mode generates one self-contained prompt per task.

What is the difference between CHAIN and FAN-OUT prompt modes?

CHAIN is sequential: each stage depends on the previous stage's output and emits the next prompt. FAN-OUT is for independent pieces sharing stable context, run in any order, with an optional collector prompt that reconciles results.

When should I not use prompt chaining?

Skip it for single-step tasks, work that fits in one session without context overflow, open-ended exploration without clear deliverables, and same-session parallelism, where parallel subagents are the better fit.

How does prompt chaining prevent context loss between chats?

Each prompt copies stable context verbatim (workspace, constraints, authority) and updates dynamic context (current state, decisions, failed approaches). The next chat receives everything it needs with zero memory of the previous one.

What happens when a stage in a prompt chain gets blocked?

The stage emits a CHAIN PAUSED block with what was done, the blocker, and one direct question instead of guessing. You answer, then resume by pasting the same stage prompt with your decision added.