06ae605051
Address findings from pedagogical review simulating a non-expert user: - Add CLAUDE.md to project root (was referenced but missing) - Fix README score from 12/9/1 to 13/8/1 (match feature-map.md) - Add Expected Output sections to examples 01, 02, 05, 09, 10 - Create pipeline-output/ and briefings/ directories - Add example ordering guidance in README - Add plan requirements for examples 11/13 in prerequisites - Add skill frontmatter explanation in GETTING-STARTED.md - Explain Cowork/Dispatch with links in cowork-integration - Expand .gitignore with node_modules and generated output files - Add model override hints in agent frontmatter comments Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
111 lines
3.6 KiB
Markdown
111 lines
3.6 KiB
Markdown
# Example 10: Full Pipeline
|
|
|
|
**Capability:** A complete workflow combining web search, multi-agent orchestration,
|
|
file I/O, memory, hooks, and logging in a single Claude Code run.
|
|
|
|
**OpenClaw equivalent:** End-to-end agent pipeline with messaging, skills, and hooks.
|
|
|
|
---
|
|
|
|
## What This Demonstrates
|
|
|
|
Every capability from examples 01-09 working together:
|
|
|
|
| Step | Capability | Example |
|
|
|------|-----------|---------|
|
|
| 1 | Web search | 03-web-search |
|
|
| 2 | Researcher agent | 06-multi-agent |
|
|
| 3 | Writer agent | 06-multi-agent |
|
|
| 4 | Reviewer agent | 06-multi-agent |
|
|
| 5 | File I/O | 02-shell-and-files |
|
|
| 6 | Memory update | 05-memory-system |
|
|
| 7 | Security logging | 09-security-hooks |
|
|
| 8 | Agent runtime loop | 01-agent-runtime |
|
|
|
|
---
|
|
|
|
## The Prompt
|
|
|
|
```
|
|
Run a full research-to-output pipeline on the topic: "How Claude Code handles
|
|
permission modes: plan, autoEdit, and bypassPermissions"
|
|
|
|
Pipeline steps:
|
|
1. Use the researcher agent to gather information from the web and official docs
|
|
2. Pass the research to the writer agent to draft a 400-word explainer
|
|
3. Send the draft to the reviewer agent for accuracy and clarity feedback
|
|
4. Incorporate the reviewer's feedback into a final version
|
|
5. Save the final version to pipeline-output/permission-modes.md
|
|
6. Append a pipeline execution summary to memory/pipeline-log.md with:
|
|
- Date and time
|
|
- Topic researched
|
|
- Word count of final output
|
|
- Any issues encountered
|
|
7. Show me the first 10 lines of the output file to confirm everything worked
|
|
```
|
|
|
|
---
|
|
|
|
## What Happens
|
|
|
|
Claude Code will coordinate the full pipeline autonomously:
|
|
|
|
- The researcher agent uses WebSearch and WebFetch
|
|
- The writer agent produces structured prose
|
|
- The reviewer agent critiques and returns specific feedback
|
|
- A revision loop runs if needed (bounded by maxTurns in settings.json)
|
|
- File writes are intercepted by PostToolUse for audit logging
|
|
- Memory is updated so the next session knows this pipeline ran
|
|
|
|
You will see each agent invocation streamed in sequence. The entire pipeline
|
|
typically completes in 2-4 minutes depending on web fetch latency.
|
|
|
|
---
|
|
|
|
## Expected Output
|
|
|
|
The pipeline takes 2-4 minutes. You will see agent invocations streaming:
|
|
|
|
1. **Researcher agent** runs WebSearch and WebFetch (30-60 seconds)
|
|
2. **Writer agent** produces a ~400-word draft (15-30 seconds)
|
|
3. **Reviewer agent** critiques the draft (15-30 seconds)
|
|
4. **Revision** if needed (15-30 seconds)
|
|
5. **File writes** to pipeline-output/ and memory/
|
|
|
|
When complete, two new files exist:
|
|
|
|
`pipeline-output/permission-modes.md` (the article):
|
|
```markdown
|
|
# How Claude Code Handles Permission Modes
|
|
|
|
Claude Code provides three permission modes that control how much
|
|
autonomy the agent has...
|
|
[~400 words with accurate technical content]
|
|
```
|
|
|
|
`memory/pipeline-log.md` (the execution log):
|
|
```markdown
|
|
## Pipeline Run - March 26, 2026
|
|
|
|
- **Topic:** How Claude Code handles permission modes
|
|
- **Word count:** 412
|
|
- **Issues:** None
|
|
- **Duration:** ~3 minutes
|
|
```
|
|
|
|
**How you know it worked:**
|
|
- Both files exist in the expected directories
|
|
- The article is accurate (check against `security/permission-modes-explained.md`)
|
|
- The pipeline log has today's date and a word count
|
|
- You saw three distinct agent invocations in the terminal
|
|
|
|
---
|
|
|
|
## Why This Matters
|
|
|
|
This is what Claude Code looks like as an actual agent platform, not a
|
|
chat assistant. The same architecture, with different prompts and agents,
|
|
runs the article production pipeline at `fromaitochitta.com`.
|
|
|
|
The companion repo you are reading is the minimal version of that setup.
|
|
Clone it, open Claude Code, and run this prompt to see the full stack work.
|