demo-plan
Run a demo plan with simulated work steps to showcase the TUI plan visualization feature.
- License 许可
- MIT
- 所属仓库
- kfet/fir
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- demo-plan
- override
- true
- description
- Run a demo plan with simulated work steps to showcase the TUI plan visualization feature.
02 资源文件 1
- 参考文档evals/triggers.json2.8 KB
03 SKILL.md 正文
Demo Plan
Run a simple multi-step plan, sleeping briefly between steps to simulate work. This demonstrates the plan widget, footer progress indicator, and metadata header.
Steps
- Create a plan with 5 steps, all pending except the first which is in_progress. Include metadata (see below).
- For each step in order:
- Mark the current step as
in_progress(all previous ascompleted). - Run
sleep 2to simulate work. - After the sleep, update the plan to mark that step
completedand the next onein_progress. - Always include the same metadata on every update (the plan tool replaces the full state each call).
- Mark the current step as
- After all steps complete, update the plan one final time with everything
completed.
Metadata to use
Include this metadata on every plan call:
{
"session": "demo-fleet",
"attach": "tmux attach -t demo-fleet",
"worktree": "/tmp/demo-project-wt"
}
Plan entries to use
Use these exact entries:
| # | Content | Priority |
|---|---|---|
| 1 | Analyze requirements | high |
| 2 | Set up project structure | medium |
| 3 | Implement core feature | high |
| 4 | Write tests | medium |
| 5 | Update documentation | low |
Example flow
plan: title="Demo Plan", metadata={session, attach, worktree}, step 1 in_progress, rest pending
sleep 2
plan: same title+metadata, step 1 completed, step 2 in_progress, rest pending
sleep 2
plan: same title+metadata, steps 1-2 completed, step 3 in_progress, rest pending
sleep 2
plan: same title+metadata, steps 1-3 completed, step 4 in_progress, rest pending
sleep 2
plan: same title+metadata, steps 1-4 completed, step 5 in_progress
sleep 2
plan: same title+metadata, all completed
After the final update, print a short congratulations message.
04 同仓库更多 Skills
wt
Spawn a fresh fir agent in its own tmux session on its own git worktree. Use whenever the user wants the work — or the conversation about the work — to happen over there, not here. If the user points at this skill, or has directly loaded it in the context, that alone is the cue — spawn, don't inline.
wrap-up
Wrap up work on a project branch — review, fix, and simplify in a loop until clean, then ff-merge to main.
tmux-observer
Attach a tmux window to an already-running fir session — observe its transcript and drive its input via tmux send-keys. Use when you need to watch or steer another fir agent.
tmux-driver
Drive interactive CLIs (python, gdb, etc.) via named tmux sessions with multi-window support. Falls back to fir's built-in PTY driver when tmux is unavailable.
telegram-bot-setup
Set up a new Telegram bot channel for a fir project — install the telegram MCP, create a per-project state dir, drop in the bot token, wire .fir/mcp.json with TELEGRAM_STATE_DIR, pair the user, and verify. Use when the user asks to add, configure, or onboard a Telegram bot for a fir worktree/project.
sync
Sync with an upstream source repo — detect changed files, apply equivalent downstream edits, update the baseline, and report any new features or non-trivial changes picked up.