smith-plan

Automates portable plan progress tracking across iterations for multi-step tasks.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/tianjianjiang/smith --skill smith-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smith-plan
Source: https://github.com/tianjianjiang/smith/tree/main/smith-plan
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan progress is often scattered across documents and tools. This Protocol provides a portable, iterative method to track plan progress across iterations, enabling consistent updates and clear signals for blockers and completion.

Core Features & Use Cases

  • Portable, platform-agnostic plan tracking across iterations
  • Checkpoint-based progress with mandatory sync after each task
  • Clear blockers and completion signaling with a defined workflow

Quick Start

Create a plan file and begin tracking iterations by completing the first unstarted task, then syncing progress after each step.

Frequently Asked Questions about smith-plan

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

FAQPage Schema
How do I track plan progress across multiple iterations with an AI agent?▼

Portable plan tracking works by mandating file updates after every task using a checkbox-based format, enabling platform-agnostic agents to synchronize progress, signal blockers, and confirm completion across iterations.

Can I use a checklist-based workflow to track blockers on any platform?▼

Yes, this checklist-based workflow operates platform-agnostically with any AI agent capable of reading and writing files, allowing you to track blockers and completion signals without platform-specific dependencies.

What is the best way to synchronize multi-step task progress with AI?▼

The best way to synchronize multi-step task progress is to follow a defined plan-sync workflow that requires updating the plan file after completing each task and explicitly recording any blockers.

Does iterative plan tracking require specific platform dependencies?▼

Iterative plan tracking requires no specific platform dependencies, functioning platform-agnostically with any AI agent capable of reading and writing files to manage your task progress.

Why should I use a portable protocol instead of platform-specific plan tracking?▼

You should use a portable protocol to prevent plan progress from being scattered across documents and tools, ensuring consistent updates and clear signals for blockers across different platforms.