autoforge

Convert system design documents into working code via multi-agent orchestration.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/wangzw/cofounder --skill autoforge-wangzw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoforge
Source: https://github.com/wangzw/cofounder/tree/main/skills/autoforge
Command: npx skills add https://github.com/wangzw/cofounder --skill autoforge-wangzw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires , and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of turning a finalized system design into tested, PRD-validated code, streamlining the development workflow and reducing manual effort.

Core Features & Use Cases

  • System Design Implementation: Converts system design documents into working code automatically.
  • Multi-Role Team Orchestration: Manages a team of planners, developers, testers, and reviewers to execute the implementation.
  • Feature-Scope Mode: Allows implementation of specific features, not the entire system design.
  • Reverse Alignment Detection: Ensures that code changes match the original PRD feature files.
  • Evolution Mode: Applies updates to existing codebase based on in-place mutations from the system-design skill.
  • Use Case: For a project with a completed system design, use this Skill to automatically generate the codebase, ensuring it matches the design and passes all tests.

Quick Start

Run the /autoforge command with the path to the system design directory.

Frequently Asked Questions about autoforge

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

FAQPage Schema
How do I automate code generation from a system design document?

Automated code generation from a system design document requires a structured design directory with API contracts and a PRD. A multi-agent orchestration model converts finalized specifications into tested code using a DAG-based scheduler for parallel module execution.

What is needed to convert system design specifications into working code?

Converting system design specifications requires a finalized design document containing module specifications, API contracts, and a PRD. The automation process orchestrates planners, developers, testers, and reviewers to validate the codebase against the original feature files.

Can I generate code for specific features instead of the entire system design?

Generating code for specific features is supported using the feature-scope mode. This allows targeted implementation of individual components rather than the entire system, applying reverse alignment detection to ensure output matches the original PRD.

Does automated implementation work with existing codebase updates?

Automated implementation works with existing codebase updates through the evolution mode. This applies in-place mutations from the system design to the current codebase, ensuring incremental changes align with the updated specifications.

What is the best way to orchestrate multi-role teams for software development?

Orchestrating multi-role teams for software development is managed through a multi-agent model using a DAG-based scheduler. This coordinates planners, developers, testers, and reviewers to execute module development, testing, and review phases in parallel.