{
"assumptions": .
---
## Advanced Moves for Power Users
- **Branch-and-merge:** Generate multiple options in parallel, then run a compare-and-select step.
- **Few-shot within steps:** Show miniature examples to guide style or structure.
- **Programmatic chaining:** Use a script to pass outputs between steps with JSON validation.
- **Retrieval inserts:** Pull relevant context (docs, FAQs) into specific steps.
- **Tool use:** At a given step, ask the model to generate code, then run it, then feed back results.
A number of tutorials teach these patterns explicitly—breaking big tasks into smaller, logical steps and orchestrating them into a pipeline.
---
## Ready-Made Chain Blueprints by Use Case
### Product Launch Copy
1) Audience and angle clarification → 2) Positioning statements → 3) Feature–benefit mapping → 4) Draft landing page → 5) Edit for clarity and conversion → 6) Final QA.
### Technical Spec Writing
1) Requirements capture → 2) Architecture options → 3) Trade-off analysis → 4) Chosen design → 5) Implementation plan → 6) Risk register.
### Customer Support Playbooks
1) Ticket taxonomy → 2) Macro templates → 3) Escalation rules → 4) QA sampling → 5) Tone calibration → 6) Localization.
---
## Implementation: Turning Chains Into Repeatable Workflows
- Use a document with headings for each step and paste outputs in sequence.
- For recurring work, convert steps into a checklist or Notion template.
- For teams, standardize schemas and rubrics so outputs are interchangeable.
- For developers, wire steps in code and validate with JSON schemas.
Worth noting: if you work inside Chrome or documents, a sidebar assistant like [Sider.AI](https://sider.ai) can help you run prompt chains right where you work—summarize a page, draft an outline, critique a paragraph, then revise—all in context. That keeps the chain tight, reduces copy-paste, and makes multi-step tasks faster. You can explore it at
---
## A Simple, Reusable Prompt Chain Template
Copy, paste, and adapt:
```markdown
Goal: [Define success in one sentence]
Context: [Audience, tone, constraints]
Step 1 — Clarify
Instruction: Restate my goal, list assumptions, risks, and open questions.
Output: JSON with keys: assumptions, constraints, open_questions.
Step 2 — Plan
Instruction: Propose a 5–8 item plan with estimated effort and success criteria.
Output: Markdown list.
Step 3 — Produce
Instruction: Create the first draft according to the plan.
Output: Structured draft.
Step 4 — Critique
Instruction: Score against rubric (accuracy, completeness, clarity, style, usefulness). Add concrete fixes.
Output: Table of scores + fix list.
Step 5 — Revise
Instruction: Apply fixes and return the final.
Output: Final artifact. If any rubric score <5, loop to Step 4.