mad-full

Automate the end-to-end feature development pipeline from natural language to merged pull request.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mad-full
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/mad-full
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-full

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating the full feature development lifecycle from initial idea to merged pull request is error-prone, inconsistent, and time-consuming, requiring teams to manually manage specifications, plans, task tracking, implementation, testing, and PR reviews across multiple disconnected steps. This Skill eliminates that overhead by automating the entire MAD pipeline with built-in quality guardrails and error recovery.

Core Features & Use Cases

  • Full Pipeline Orchestration: Automates the complete end-to-end feature development workflow (specify → plan → tasks → implement → validate → commit → PR) with mandatory quality review gates at each phase to catch issues early.
  • Adaptive Workflow Depth: Automatically triages feature complexity (trivial, standard, complex) to skip unnecessary steps for small changes like typo fixes, while running deep research for architectural changes.
  • Parallel Agent Coordination: Leverages Agent Teams to run parallel validation lenses, implementation workers, and research scouts to speed up workflow execution without manual coordination.
  • Multiple Execution Modes: Supports interactive mode with user checkpoints for learning, autonomous mode for unattended overnight runs, and headless JSON output for CI/CD integration.
  • Error Recovery: Includes built-in recovery logic for test failures, build errors, and gate failures, with automatic retry logic and progress checkpoints to resume interrupted runs.
  • Use Case: A developer can provide a natural language request like "add OAuth2 user authentication" and automatically generate the full specification, implementation plan, task list, write and test the code, and open a PR for review without manually coordinating each step.

Quick Start

Use the mad-full skill by providing your natural language feature description to automatically run the complete end-to-end development pipeline from specification through merged pull request.

Frequently Asked Questions about mad-full

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

FAQPage Schema
How do I automate feature development from a natural language idea to a merged pull request?

Automating feature development from idea to merged PR requires an end-to-end pipeline that orchestrates specification, planning, implementation, and validation steps with built-in quality gates. This Skill automates that entire workflow, taking natural language input and generating the code and PR automatically.

Can I run automated code generation and pipeline orchestration in headless CI/CD environments?

Yes, automated code generation and pipeline orchestration can run in headless CI/CD environments using headless JSON output mode. This allows unattended overnight execution with built-in error recovery and automatic retry logic for test or build failures.

How does automated workflow orchestration handle trivial fixes versus complex feature requests?

Automated workflow orchestration applies adaptive workflow depth by triaging feature complexity. It skips unnecessary steps for trivial changes like typo fixes, while running deep research and parallel agent coordination for complex architectural requests.

What is the best way to coordinate parallel agents for software engineering tasks?

The best way to coordinate parallel agents for software engineering tasks is using a pipeline that leverages agent teams to run parallel validation lenses, implementation workers, and research scouts. This speeds up workflow execution without requiring manual coordination.

Does automated pull request generation work with TypeScript and Electron stacks?

Yes, automated pull request generation supports software engineering teams building features with TypeScript and Electron stacks. The pipeline writes, tests, and commits the code before opening a PR for review.

Why do automated build and test failures interrupt my feature development pipeline?

Automated build and test failures interrupt pipelines due to validation gate checks failing. This Skill includes built-in error recovery logic with automatic retry mechanisms and progress checkpoints to resume interrupted runs without losing work.