open/claude-code-complete-agent
1
0
Fork 0
Code Activity Actions

feat: make examples cumulative with carry-forward chain and capstone

Browse source 
Add three new sections to all 14 examples:
- "Carry Forward": what output feeds into later examples (01-10)
- "The Cumulative Path": alternative prompt building on previous output (02-10)
- "Now Try It Yourself": personalized template with transferable pattern (all)
- "Building On" callout connecting back to previous examples (02-10)

Add Example 14: Build Your Personal Agent - capstone that guides reader
through writing their own CLAUDE.md, creating a personal skill, connecting
a messaging channel, setting up automation, and testing end-to-end.

Update README with cumulative path diagram, two usage modes, and example 14.
Update GETTING-STARTED.md with cross-references to relevant examples.

17 files changed, 703+ lines added. The examples now form a coherent
learning path from "see what it can do" to "build your own agent."

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-03-26 21:14:35 +01:00
commit 0d0b83f98c
17 changed files with 979 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

55
examples/07-messaging/prompt.md
View file

@ -6,6 +6,8 @@ Native Telegram support arrived in v2.1.80. Other channels use MCP servers.
**OpenClaw equivalent:** 15+ native channels (WhatsApp, Telegram, Discord, Slack,
Signal, iMessage, IRC, Matrix, Teams, and more).
> **Building on Example 06.** You have a polished, reviewed document from the multi-agent cycle. This example shows how to deliver that result to your phone. A pipeline that produces output nobody sees is a pipeline that does not matter.
---
## Architecture Difference
@ -81,3 +83,56 @@ Both confirm delivery in the terminal output.
If you need 15 channels working out of the box, OpenClaw wins today. Claude Code
has Telegram natively and the rest via MCP. The gap is narrowing with each
release. For most personal automation needs, Telegram is sufficient.
---
## Carry Forward
You now have a delivery channel. Combined with what came before:
- **Example 08** schedules the pipeline so results arrive automatically
- **Example 10** produces pipeline output that you can deliver via messaging
- **Example 12** expands this into full remote access from your phone
Messaging turns Claude Code from "a tool at my desk" into "an assistant I can reach from anywhere."
---
## The Cumulative Path
> If you ran Example 06, you have `pipeline-output/research-report/final-summary.md`.
> This prompt delivers it to your phone.
**Telegram:**
```
Read pipeline-output/research-report/final-summary.md. Send the first
paragraph as a Telegram message with the note: "Full report saved to
pipeline-output/research-report/. Run /read-report to see the rest."
```
**Slack:**
```
Read pipeline-output/research-report/final-summary.md. Post the first
paragraph to #[your-channel] with a thread reply containing the full
summary. Use the /send-slack-message skill.
```
After running this, your pipeline has end-to-end delivery. Research goes from web to your phone in one flow.
---
## Now Try It Yourself
Set up the channel that fits your workflow:
```
Send a [Telegram/Slack/Discord] message to [destination] with:
"[summary of what your pipeline produced]"
```
**The pattern you just learned:** read output + format for channel + deliver. Any pipeline step can send a notification. Typical triggers: pipeline completed, error occurred, daily summary ready.
Ideas worth trying:
- Morning briefing delivered to your phone at 07:00
- Slack notification when a scheduled report finishes
- Error alerts when a cron job fails