DualForge-Workflow README

The project's README from github.com/zc8163623/DualForge-Workflow. As one markdown file: README.md.

DualForge Workflow

Dual AI Collaboration Framework Builder — Establish a clear division of labor between Claude + Codex for new projects

中文文档

🎯 Core Concept

Establish a clear AI collaboration system:

Workflow: Human → Claude (Plan) → Codex (Implement) → Claude (Review) → Human (Decision)

📦 What This Skill Does

Build a complete dual AI collaboration framework from scratch, including:

  1. PRD Co-creation: Conversational guidance to complete Product Requirements Document
  2. Collaboration Standards Generation: Auto-generate CLAUDE.md and AGENTS.md behavior specifications
  3. Documentation System: Create .ai/brief.md, plan.md, review.md, decision-log.md
  4. Verification Script Framework: Generate executable frameworks for scripts/check.sh, build.sh, test.sh
  5. Handoff Mechanism: Built-in quick-switch phrases to solve collaboration breakpoints

🚀 Usage

1. Install Skill

Choose your language:

(Specific path depends on your Claude configuration)

Note: The skill will generate documents in the language you use during conversation. You can mix languages freely (e.g., English conversation → English PRD, Chinese conversation → Chinese PRD).

2. Invoke Skill

In a Claude conversation, type:

/DualForge-Workflow

Or simply say:

I want to set up a dual AI collaboration framework

3. Follow the Process

The skill will guide you through 4 stages:

📂 Generated File Structure

project/
├── PRD.md                    # Product Requirements Document
├── CLAUDE.md                 # Claude behavior specification
├── AGENTS.md                 # Codex behavior specification
├── GETTING_STARTED.md        # Getting started guide
├── scripts/
│   ├── check.sh             # Verification script framework
│   ├── build.sh             # Build script framework
│   └── test.sh              # Test script framework
├── src/                      # Source code root directory
└── .ai/
    ├── brief.md             # Entry point + collaboration contract
    ├── plan.md              # Project plan
    ├── review.md            # Review checklist
    ├── decision-log.md      # Architecture Decision Records
    └── tasks/
        └── _TEMPLATE.md     # Task template (optional)

📋 Live Example

See a complete example of generated framework in examples/small-project-todoapp/

TodoApp - Small Project Example

A task management tool for teams of 10-20 people. Generated in ~15 minutes of conversation.

File Structure:

todoapp/
├── PRD.md                          # 7 functional requirements with acceptance criteria
├── CLAUDE.md                       # Claude work specifications
├── AGENTS.md                       # Codex work specifications
├── GETTING_STARTED.md              # Step-by-step guide
├── scripts/
│   ├── check.sh                   # ✓ Format → Lint → Types → Tests
│   ├── build.sh                   # ✓ Build with Vite
│   └── test.sh                    # ✓ Run Vitest + coverage report
├── src/
│   └── README.md                  # Architecture notes
└── .ai/
    ├── brief.md                   # Project context + quick-switch phrases
    ├── plan.md                    # 13 tasks across 4 stages
    ├── review.md                  # Review checklist
    └── decision-log.md            # 1 ADR (tech stack selection)

Key Highlights:

Sample from PRD.md:

### FR-3 Status Management

**Description**: Tasks have four statuses and transition in a fixed order.

**Status Definitions:**
1. **To Do**: Task created, not yet started
2. **In Progress**: Task is being executed
3. **In Review**: Task completed, awaiting team confirmation
4. **Done**: Task approved and completed

**Transition Rules:**
- Status transitions in order: To Do → In Progress → In Review → Done
- Cannot skip statuses
- Can roll back to previous status
- All team members have permission to modify task status

**Acceptance Criteria:**
- [ ] New tasks default to "To Do" status
- [ ] Can only advance in order
- [ ] Can roll back to previous status
- [ ] Status changes immediately reflected in interface

Sample from scripts/check.sh:

#!/bin/bash
# Stage 4: Lint
echo "🔍 Running ESLint..."
npm run lint
if [ $? -ne 0 ]; then
    echo "❌ Lint failed"
    exit 1
fi

# Stage 5: Type Check
echo "📘 Running TypeScript type check..."
npm run type-check
if [ $? -ne 0 ]; then
    echo "❌ Type check failed"
    exit 1
fi

→ Explore the complete example

✨ Key Features

1. Smart Project Scale Adaptation

2. Optional Task File Mechanism

3. Solves Handoff Breakpoints

4. Complete Verification System

🎨 Use Cases

✅ Suitable for:

❌ Not suitable for:

📖 Workflow Example

You: I want to build a task management system
  ↓
Claude invokes DualForge-Workflow skill
  ↓ Guides through PRD completion
Claude generates complete collaboration framework (13 files)
  ↓
You: Implement user login feature
  ↓
Claude produces task file .ai/tasks/1.1-user-login.md
       + Outputs handoff instructions
  ↓ Copy handoff instructions to Codex
Codex implements according to plan + tests + check.sh
       + Updates status
       + Proactively requests Review
  ↓ Copy Review request to Claude
Claude reviews and gives conclusion (can merge / needs changes / wrong direction)
  ↓
You: Decide whether to merge

🔧 Configuration Options

Project Scale

Tech Stack

Supports any tech stack, skill generates corresponding script examples based on your input:

Test Coverage

📚 Documentation

🤝 Contributing

Issues and Pull Requests are welcome!

📄 License

MIT

Make AI collaboration clearer, make development more efficient.

DualForge-Workflow (zc8163623/DualForge-Workflow)

Searching Database…

195 ·GitHub
DualForge-Workflow
What is this?DualForge Workflow is a Claude Skill that builds a full collaboration framework for AI-assisted coding projects, splitting the work so Claude plans and reviews while Codex implements, with a human making the final calls.
Is this a coding tool or just a set of document templates?It's a Claude Skill — a markdown instruction file that Claude reads to interactively generate a full set of collaboration documents and verification scripts for your project, not a standalone app.
How do I install and use it?Save SKILL.md (English) or SKILL.zh-CN.md (Chinese) into your Claude skills library, then invoke the skill in a Claude conversation; it guides you through 4 stages to generate 13 framework files.
Do I need Codex as well as Claude to actually use this workflow?Yes — the framework assumes Claude handles planning, design, and review while Codex does the coding and testing, so both tools are expected to be part of the setup.
Is this useful for quick scripts or small experiments?No — the author says it's not suited for one-off scripts, experimental projects, or unclear exploratory work; it's built for projects with clear requirements, long-term iteration, or team collaboration.
What files does it actually generate?It creates CLAUDE.md and AGENTS.md behavior specs, a documentation system (.ai/brief.md, plan.md, review.md, decision-log.md), and verification scripts (check.sh, build.sh, test.sh) — 13 files in total.
Does it work with any tech stack?Yes, it supports any tech stack — TypeScript/JavaScript, Python, Go, Rust, Java and more — and generates matching script examples based on your input.
What does the generated check.sh actually verify?It runs a 7-stage pipeline covering structure, boundaries, format, lint, types, and tests.
Is there a worked example I can look at?Yes, a complete generated framework for a small TodoApp project (PRD, plan, and scripts) is included in examples/small-project-todoapp/.
What are similar projects?pstack, pstack-claude, specweave, superpowers-zh, spec-kit, shuohao-skills, harness, ProductSpec
Which topics is it in?spec-driven-development, project-management, template, agent-framework, workflow, skill, multi-agent, documentation, coding-agent, claude, markdown, agent-skills
Creator
zc8163623
Size
0.1 MB
Stars
195
Updated
CommitAug 15
Age
2mo
Commits · 90 Days