Skip to content

Dong90/oh-my-taiyiforge

Repository files navigation

English · 简体中文

TaiyiForge

Turn six AI engineering standards into a single executable nine-stage R&D workflow

License: MIT Node

Version v28 canonical CI Platforms

Document-driven AI R&D with gates, not vibes.

Stop memorizing the phase order. Say /taiyi:new and the engine tells you what's next.

Quick Start · Usage Guide · Architecture · Command Reference · Full Flow · Contributing


TaiyiForge Architecture — Six standards × Workflow engine × Nine stages × Skill universe × Three-layer gates

4K visual poster (non-technical source) · Editable source: SVG · C4


1 · The Problem

Real terminal demo

27-second real terminal recording · asciicast source (playable on asciinema.org or locally with asciinema play docs/diagrams/demo.cast)

Every team using AI for serious work has hit some version of these:

Pain you've hit Why it bites
Agent forgets the phase order mid-task and jumps to code Lost context, half-baked designs, untested changes — review has to redo the work
Context explodes mid-change, requirements / design / code all lost Long sessions die; resume from chat is impossible
Each of OpenCode / Claude / Codex / Cursor has its own ad-hoc flow Same feature, four different rituals — onboarding is per-tool, not per-team
Even a typo fix has to go through nine stages Rigid pipelines kill momentum on small fixes
Don't dare let AI decide at critical nodes "Looks good" review without a human sign-off is gambling with prod
Don't know what the installed Skills are actually doing Drift between docs and installed behavior, no audit trail
Want to coexist with OMC / OMX Lock-in to one orchestrator stack kills composability

TaiyiForge's answer to every one of these is in §2 The Solution.


2 · The Solution

A single nine-stage artifact contract + 28 v28 slashes + 6 umbrellas + one /taiyi:* vocabulary that works the same on all four AI harnesses.

v28 = 推荐命名 + 顶栏收敛,Cursor/Claude 仍装全 prompt。Phase 2(IDE 菜单裁剪)未做,见 canonical-commands.md

TaiyiForge does not invent standards — it orchestrates Harness · OpenSpec · GStack · Superpowers · OMO · Spec-Kit into one state machine. Use what you have installed; everything else is auto-skipped as optional.

2.1 · The Nine-Stage Workflow

One change = one slug, sequential execution, fixed artifacts. Human gates require --approver before the engine lets you pass.

# Phase Category Skill Artifact Notes
1 change Human gate taiyi-change CHANGE.md 3-5 paragraph proposal with scope
2 requirement Auto taiyi-requirement REQUIREMENT.md Acceptance criteria + AC checkbox
3 design Human gate taiyi-design DESIGN.md ≥2 options compared + decision
4 ui-design Auto taiyi-ui-design UI-DESIGN.md Only for changes that touch UI
5 task Auto taiyi-task TASK.md Slice into independently-PR-able pieces
6 dev Auto taiyi-dev TDD test + minimal impl TDD forced — red first, then green
7 test Auto taiyi-test TEST.md Summary kept; E2E runs in CI
8 review Human gate taiyi-review REVIEW.md Cross-AI review + high-severity must-fix
9 integration Auto taiyi-integration CHANGELOG.md merged Delivery gate: audit + deliveryVerifyCmd
archive Cleanup taiyi-integration .taiyi/archive/ Only after all nine stages pass

Full command list → canonical-commands.md · Artifact layout → artifact-layout.md

2.2 · v28 Slash Catalog (28)

Source of truth: canonical-commands.mdcanonical_v28. Legacy slashes still work, see Legacy 兼容.

# Group Slash Purpose
1–6 Main chain new · status · write · continue · apply · archive Daily shortest path
7–10 Session handoff · resume · cancel · list Cross-session
11–13 Diagnose doctor · audit · verify Self-check + delivery gate
14–17 Delivery commit · ship · land · release gstack delivery chain
18–19 Routing gstack <skill> · sp <skill> External harness routing
20–22 Stage shortcuts explore · tdd plan|dev · flow Skip the nine-stage
23–28 Umbrellas (6) token … · test … · review … · diagram … · mode … · workflow … Domain multi-subcommand

Daily shortest path:

/taiyi:new → /taiyi:write → /taiyi:continue → /taiyi:apply → … → /taiyi:commit → /taiyi:continue integration → /taiyi:archive

Umbrella quick map (full map in canonical-commands.md §伞形命令·子命令地图):

Umbrella Sub-commands Count
/taiyi:token status · record · scan · compress 4
/taiyi:test smoke · e2e · qa · ui · security 5
/taiyi:review loop · check · health · gstack 4
/taiyi:diagram pipeline · c4 · arch · render · flow 5
/taiyi:mode ralph · autopilot · daemon · team · ultrawork · agent · step · stop · list · keyword · preflight 11
/taiyi:workflow plan · ralplan · loop · check · run · sync · ccg · sciomc · deepinit · remember · ultraqa 11

2.3 · Legacy 兼容

Legacy slashes & CLI still work — listed in canonical-commands.md §Legacy 兼容. Don't add new top-bar duplicates of v28 umbrellas.

曾用 / legacy v28 现用
/taiyi:pause /taiyi:handoff
/taiyi:state · /taiyi:state-read /taiyi:status
/taiyi:next · /taiyi:done /taiyi:status + /taiyi:continue
/taiyi:change/taiyi:integration /taiyi:write
/taiyi:ralph 等 OMC /taiyi:mode ralph
npx taiyi new · npx taiyi walkthrough /taiyi:new · /taiyi:flow help

3 · The Evidence

3.1 · One Skill Set, Four Harnesses

One node scripts/taiyi-forge.sh install --all syncs to all four harnesses; missing ones are auto-skipped. Same 28 v28 顶栏 slashes, same taiyi-* Skills — different chat syntax & MCP surface per harness:

Harness Chat entry Engine entry MCP Hook / keyword Read more
Claude Code /taiyi:new … /taiyi:archive + Skill + ~/.claude/commands/taiyi-*.md Agent Bash taiyi_doctor · taiyi_audit keyword hook control-plane.md §四端对照
Codex $taiyi-new$taiyi-archiveprompts/taiyi-*.mdnot /taiyi:* Agent 跑 scripts/taiyi-forge.sh 无(靠 shell) codex-keyword-preflight.mjs + developer_instructions~/.codex/config.toml control-plane.md §Codex
Cursor /taiyi:new … /taiyi:status + taiyiforge.mdc rule + ~/.cursor/commands/taiyi-*.md Agent 终端 / MCP taiyi_doctor · taiyi_audit keyword hook mcp-setup.md
OpenCode taiyi_new / taiyi_* plugin tools + ~/.config/opencode/commands/taiyi-*.md plugin + /taiyi-* 斜杠 (插件内置) plugin 自管 control-plane.md §OpenCode

Codex 注意:chat entry is the $taiyi-* keyword (not /taiyi:*), routed via codex-keyword-preflight.mjs and developer_instructions. See control-plane.md.

3.2 · Chat Track vs Engine Track

Surface Used by Does what Example
Chat slash Developer / Agent Write artifact, run TDD, load specialized Skill /taiyi:write · /taiyi:apply · /taiyi:tdd dev
Engine CLI Agent / CI (run for you) Validate artifact, gates, advance phase npx taiyi continue <slug> · npx taiyi complete <slug> change --approver "…"
Shell entry Agent / CI Equivalent to CLI; written into consumer project after install scripts/taiyi-forge.sh status --json --compact
MCP Cursor etc. Read-only troubleshooting taiyi_doctor · taiyi_audit

Principle: Users only say /taiyi:*; never make the user type taiyi-forge.sh by hand. Agents read status --json --compact engineTruth; never dump full artifacts into chat.

3.3 · Architecture at a Glance

┌─────────────────────────────────────────────────────────────┐
│  Entry: taiyi CLI · taiyi-forge.sh · OpenCode plugin · MCP    │
└───────────────────────────┬─────────────────────────────────┘
                            ▼
┌─────────────────────────────────────────────────────────────┐
│  workflow-engine — intent analysis · token budget · routing · gates │
└───────────────────────────┬─────────────────────────────────┘
                            ▼
┌─────────────────────────────────────────────────────────────┐
│  .taiyi/changes/<slug>/  — CHANGE … CHANGELOG (source of truth)  │
└─────────────────────────────────────────────────────────────┘
         chat loads taiyi-* Skill to write artifacts ↑   ↓ engine validates & advances phase

4 · Quick Start

Status note: v0.23.0 is not yet published to npm. The only install path right now is from source. CI is green, npm will follow; badges will switch automatically.

Option A · Source install (recommended, ready now)

git clone https://github.com/Dong90/oh-my-taiyiforge.git
cd oh-my-taiyiforge
npm install && npm run build && npm test

Option B · Install into your project (also source)

git clone https://github.com/Dong90/oh-my-taiyiforge.git
cd oh-my-taiyiforge
npm install && npm run build

# Install to all four harnesses + optional triangles
# (OpenSpec / gstack / Superpowers / web-quality-skills)
node scripts/taiyi-forge.sh install --all

# Or one harness at a time:
node scripts/taiyi-forge.sh install --cursor
node scripts/taiyi-forge.sh install --claude --cursor
# Skip optional deps:
node scripts/taiyi-forge.sh install --all --skip-deps

Option C · Run the example projects (zero-install quick feel)

cd examples/commands-smoke
npm install
npm run chat-demo          # Chat verbs: new / status / check / continue
npm run walkthrough-e2e    # Nine-stage shell E2E + iron-triangle
# /taiyi:doctor           # Workspace + install self-check (chat slash)
Example Purpose
examples/full-flow-demo Nine-stage + slash E2E
examples/commands-smoke Command smoke tests
examples/browser-e2e-smoke CI templates
examples/verification-suite Minimal integration demo

Want npm install oh-my-taiyiforge? Wait for the Releases announcement — it'll light up here first.

Option D · Your first change (5 minutes)

# Recommended entry: auto-slug + engine guidance
npx taiyi walkthrough
npx taiyi new "Add login optimization"  # writes to .taiyi/changes/<slug>/
npx taiyi status                         # current phase + recommended Skill + next step

# Edit .taiyi/changes/<slug>/CHANGE.md, then:
npx taiyi complete <slug> change --approver "your-name"   # human gate
npx taiyi continue <slug>                                 # auto gate

# In chat (OpenCode / Claude / Cursor — Codex uses `$taiyi-*` keywords instead):
/taiyi:new "<feature title>"              # lay CHANGE.md template
/taiyi:status                             # current phase + recommended Skill + next step
/taiyi:write                              # write current phase artifact (handles 9 stages)
/taiyi:continue --approver "your-name"    # human gate (change / design / review)
/taiyi:apply                              # dev/test harness checklist
/taiyi:commit                             # post-dev commit with Taiyi-Change trailer
/taiyi:archive                            # archive after all nine stages

# Common umbrella picks:
/taiyi:doctor                             # install + workspace self-check
/taiyi:token compress <slug>              # long-session → CONTEXT-COMPACT.md
/taiyi:test smoke                         # Playwright built-in smoke
/taiyi:flow bug <slug>                    # lite path for small fixes

That's it. Phase order, artifact templates, gate validation are the engine's job. You write Markdown and code.

Agent-priority troubleshooting:

scripts/taiyi-forge.sh doctor --json --compact
scripts/taiyi-forge.sh audit --json --compact

5 · Reference

5.1 · Documentation

Document What it covers When to read
docs/QUICKSTART.md 5-minute walkthrough First install
docs/USAGE.md Scenarios · daily rhythm · delivery chain After the walkthrough
docs/ARCHITECTURE.md Architecture overview + code layout Hacking the engine / debugging
docs/taiyi/canonical-commands.md v28 slash command table Looking up a command
docs/taiyi/control-plane.md Agent discipline + token discipline Onboarding an Agent
docs/taiyi/full-oss-flow.md Superpowers + all-plugins demo Want a full end-to-end
docs/taiyi/integrations.md Iron triangle + plugin integrations Installing optional pieces
AGENTS.md Agent's read-state entry point Configuring Agents
CONTRIBUTING.md Contribution guide Before opening a PR
CHANGELOG.md Release notes Checking for updates
docs/diagrams/demo.gif Real terminal recording (27s) Quick feel of the engine
README.zh-CN.md 简体中文版 中文用户

5.2 · Development & Verification

Contributor clone:

git clone https://github.com/Dong90/oh-my-taiyiforge.git
cd oh-my-taiyiforge
npm install && npm run build && npm test
node scripts/taiyi-forge.sh install --all

Common commands:

npm test               # Vitest contracts + nine-stage E2E
npm run test:watch     # watch mode
npm run build          # TypeScript → dist/
npm run dogfood        # root repo demo (eat your own dog food)
npm run ci:platforms   # four-platform smoke (opencode/claude/codex/cursor)
npm run check:docs     # doc-vs-commands.yaml sync check

CI: .github/workflows/ci.yml — platform smoke runs across a 4 × ubuntu matrix.

5.3 · Roadmap & Status

Version Status Key milestones
v0.23.0 ✅ Released canonical v28: 28 顶栏 slashes + 6 umbrellas (token/test/review/diagram/mode/workflow) + skill-fusion-principles.md + validateV28CatalogSync gate
v0.24.x 🚧 In progress First npm release · oh-my-taiyiforge zero-build install · README v28 收敛 (this rewrite) · umbrella Phase 2 (real IDE menu trim) deferred
v1.0.0 ⏳ Planned Lock 9-stage API · 4-platform parity · external case-study collection

Ready today: full nine-stage pipeline · four-harness shared Skills · forced TDD · token compression · platform-smoke CI Not yet: one-line npm install (v0.24 target) · production-grade SLA · full i18n

5.4 · Community & Contributing

  • 🐛 Report a bug: GitHub Issues · bug label
  • 💡 Idea / RFC: Discussions
  • 🔧 Open a PR: read CONTRIBUTING.md first; npm test + npm run check:docs must be green
  • Star / Watch: drop a star to get notified on the next release
  • 🧵 Codex users: search for $taiyi-* keywords; four-harness entry decision tree in docs/taiyi/invoke.yaml

Code of conduct: follow the Contributor Covenant spirit — critique ideas, not people.

5.5 · License

MIT © 2026 TaiyiForge contributors

5.6 · Acknowledgments

Inspired by: oh-my-claudecode · oh-my-codex · Harness Engineering · OpenSpec · GStack · Superpowers · OMO · Spec-Kit.

About

TaiyiForge — nine-phase AI workflow plugin for OpenCode + taiyi-* skills for Claude/Codex

Resources

License

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors