@tianhai/pi-workflow-kit

Enforce structured brainstorm→plan→execute→finalize workflow with TDD discipline in AI coding agents

Package details

extensionskill

Install @tianhai/pi-workflow-kit from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:@tianhai/pi-workflow-kit
Package
@tianhai/pi-workflow-kit
Version
0.11.1
Published
May 5, 2026
Downloads
1,869/mo · 417/wk
Author
tianhai
License
MIT
Types
extension, skill
Size
113.5 KB
Dependencies
0 dependencies · 4 peers
Pi manifest JSON
{
  "extensions": [
    "extensions/workflow-guard.ts"
  ],
  "skills": [
    "skills"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

pi-workflow-kit

Stop AI agents from rushing to code. Enforce a structured brainstorm→plan→execute→finalize workflow with TDD discipline.

AI coding agents tend to skip design and jump straight into implementation, producing over-engineered or misaligned code. pi-workflow-kit solves this by hard-blocking write operations during brainstorm and planning phases — the agent literally cannot modify your source files until you approve the design.

pi package. Zero configuration required.

Install

pi install npm:@tianhai/pi-workflow-kit

No setup needed — skills and guards activate automatically after install.

Want to try before committing?

pi -e npm:@tianhai/pi-workflow-kit

What You Get

🛡️ Workflow Guard (extension)

Enforces phase-appropriate tool access — not just guidelines, but hard blocks:

Phase write / edit bash
Brainstorm / Plan 🔒 Blocked outside docs/plans/ 🔒 Read-only only (grep, find, cat, git status, curl…)
Execute / Finalize ✅ Full access ✅ Full access

The agent can read code and discuss design with you during brainstorm/plan, but it physically cannot modify source files or run mutating commands.

🧠 5 Workflow Skills

Guide the agent through a disciplined development process:

brainstorm → plan → execute → finalize
              ↕
           diagnose (anytime)
Phase Trigger What Happens
Brainstorm /skill:brainstorming Explore approaches, debate tradeoffs, produce a design doc
Plan /skill:writing-plans Break design into bite-sized TDD tasks with file paths and acceptance criteria
Execute /skill:executing-tasks Implement tasks one-by-one with TDD discipline and optional checkpoint review gates
Finalize /skill:finalizing Archive plan docs, update README/CHANGELOG, create PR
Diagnose /skill:diagnose 6-phase debugging loop: reproduce → hypothesize → instrument → fix → verify

The Workflow in Detail

Phase Control

You control each phase — the agent never advances on its own. Invoke a skill to move forward:

/skill:brainstorming   →  discuss and design
/skill:writing-plans   →  break into tasks
/skill:executing-tasks →  implement with TDD
/skill:finalizing      →  ship it

TDD Three-Scenario Model

Each task is labeled with its TDD scenario during planning:

Scenario When Rule
New feature Adding new behavior Write failing test → implement → pass
Modifying tested code Changing existing behavior Run existing tests first → modify → verify
Trivial Config, docs, naming Use judgment

Checkpoint Review Gates

Optionally label tasks with a checkpoint to pause for human review. At each checkpoint the agent stops and waits for your feedback — you can approve, ask for changes, or send it back to rethink. Only when you're satisfied does it move on to the next task.

Checkpoint When to Use What Happens
(none) Trivial tasks, well-understood changes Auto-advance, no pause
checkpoint: test Test design matters Agent writes the failing test, then pauses for your review. Verify the test covers the right cases before the agent implements.
checkpoint: done Implementation review matters Agent implements and passes tests, then pauses for your review. Verify the implementation is correct before committing.

Quick Start

# Install
pi install npm:@tianhai/pi-workflow-kit

# Start a new feature
> /skill:brainstorming
> I want to add OAuth2 login to our API

# (agent explores approaches, writes design doc)
# (write/edit are blocked — your code is safe)

> /skill:writing-plans

# (agent breaks design into TDD tasks)
> /skill:executing-tasks

# (agent implements with TDD, all tools unlocked)
> /skill:finalizing

# (agent archives docs, updates changelog, creates PR)

Why?

  • AI agents skip design. Left unchecked, they jump to code and over-engineer. This forces a think-first workflow.
  • TDD needs structure. The three-scenario model gives the agent clear rules for when to write tests first.
  • You stay in control. Checkpoint review gates let you approve test designs and implementations before the agent commits.
  • Enforced, not suggested. Hard blocks mean the agent can't ignore the rules — not even accidentally.

Project

pi-workflow-kit/
├── extensions/
│   └── workflow-guard.ts      # Write blocker during brainstorm/plan
├── skills/
│   ├── brainstorming/SKILL.md
│   ├── writing-plans/SKILL.md
│   ├── executing-tasks/SKILL.md
│   ├── finalizing/SKILL.md
│   └── diagnose/SKILL.md
├── tests/
│   └── workflow-guard.test.ts
├── package.json
└── README.md

Development

npm test

License

MIT