Skip to main content
prompt GP ChatGPT

taiyi-forge — Claude Code prompt: manage development phases

A Claude Code prompt that runs the TaiyiForge engine—a development state machine with init, next, harness, and continue commands. Orchestrates project phases via shell script and tracks state without guessing.

MIT ★ 855 updated 2026-10-12

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/taiyi-forge.md
Open on GitHub

What taiyi-forge does

TaiyiForge is a phase-based state machine. The prompt parses arguments and calls scripts/taiyi-forge.sh from your project root. Four core commands: init starts a new phase with a name and optional --auto flag for automated progression; next moves to the next phase; harness and harness-check validate readiness; continue completes the phase and locks progress. The prompt never marks a phase done until continue succeeds—no assumptions about state.

Each phase loads its own skill prompts (taiyi-*) for artifact writing. In --auto mode, checks run automatically before each continue. Install by copying .claude/commands/taiyi-forge.md into your project.

What it helps with

  • start and track a development phase from Claude Code
  • advance to the next phase only when the current one is ready
  • run validation checks automatically before completing a phase
  • manage multi-phase projects without losing context across calls

Example prompts for the agent

  • Start a phase: $taiyi-forge init auth-fix --auto --title "Auth fix"
  • Move to the next phase: $taiyi-forge next auth-fix
  • Check readiness: $taiyi-forge harness auth-fix

How to install taiyi-forge

Manually: put the files in place

.claude/commands/taiyi-forge.md

Questions about taiyi-forge

How do I install taiyi-forge in Claude Code?

Copy .claude/commands/taiyi-forge.md into your project's .claude/commands/ directory. Then invoke it as $taiyi-forge <command> <args>.

What does taiyi-forge do?

It manages development phases via a state machine. Commands init, next, harness, and continue execute the shell script and track progress. The prompt does not mark a phase complete until continue returns success.

What is the --auto flag?

When you pass --auto during init, validation checks (harness and harness-check) run automatically before each continue to confirm the phase is ready to advance.

Source text

taiyi-forge.md · MIT
---
description: "TaiyiForge engine control — init, next, harness, continue (OMX-style)"
argument-hint: "subcommand and args, e.g. next my-feature"
---
<identity>
You are the TaiyiForge engine operator. You run the workflow state machine via shell, not by guessing phase state.
</identity>

<constraints>
- Always execute `scripts/taiyi-forge.sh` (or `./node_modules/oh-my-taiyiforge/scripts/taiyi-forge.sh`) from the project root.
- Never claim a phase is complete without a successful `continue` command output (CLI alias: `complete`).
- For artifact writing, load the matching `taiyi-*` phase skill; this prompt is engine-only.
- In `--auto` mode, run `harness` and `harness-check` before each `continue`.
</constraints>

<usage>
Examples:
- `$taiyi-forge next auth-fix`
- `$taiyi-forge harness auth-fix`
- `$taiyi-forge continue auth-fix change`
- `$taiyi-forge init auth-fix --auto --title "Auth fix"`
</usage>

When the user invokes this prompt, parse `$ARGUMENTS` as subcommand + args and run the forge script accordingly. Show stdout/stderr to the user.

{{TAIYI_STAGE_PROTOCOL}}

© Dong90 · MIT · Dong90/oh-my-taiyiforge

Similar prompts

All prompts for Agent setup: memory, context, orchestration →

From the same set4

Project sponsors

Companies that keep this analytics open