auto-coder

Synchronize project specifications into chapter references and implement the next pending task.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zhuangfanupup/modular-rag-mcp-server --skill auto-coder-zhuangfanupup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-coder
Source: https://github.com/zhuangfanupup/modular-rag-mcp-server/tree/main/.claude/skills/auto-coder
Command: npx skills add https://github.com/zhuangfanupup/modular-rag-mcp-server --skill auto-coder-zhuangfanupup

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the friction of spec-driven implementation by turning a project specification into a concrete development plan, code changes, tests, and tracked progress.

Core Features & Use Cases

  • Spec Synchronization: Reads the project spec and keeps chapter-based reference files aligned with the latest schedule and architecture details.
  • Task Discovery: Identifies the next actionable item from the roadmap, including in-progress work and the first pending task when nothing is underway.
  • Implementation Workflow: Guides autonomous coding, test execution, and iterative fixes so the work can move from requirement to validated result with minimal manual intervention.
  • Progress Persistence: Updates task status and preserves completion state so development can continue cleanly across cycles.
  • Use Case: A developer asks for one-shot implementation of the next roadmap item and gets synchronized references, code changes, passing tests, and a recorded progress update.

Quick Start

Use the auto-coder skill to sync the spec, implement the next pending task, run tests, and report the result.

Frequently Asked Questions about auto-coder

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

FAQPage Schema
How do I automate spec-driven development from requirements to passing tests?

Spec-driven development automation works by synchronizing your project specification into chapter-based references, autonomously selecting the next pending task, implementing code, running tests, and persisting progress. This workflow requires deterministic file updates and configuration-aware planning to validate results.

What is spec synchronization in an automated coding workflow?

Spec synchronization reads your project specification and keeps chapter-based reference files aligned with the latest schedule and architecture details. This ensures the autonomous task selection and implementation workflow always operates on the most current requirements.

How do I auto-fix failing pytest results during autonomous task implementation?

Auto-fixing failing pytest results during autonomous task implementation involves up to three iterative test rounds with commit-aware state tracking. The workflow executes tests, applies fixes, and tracks state to ensure code changes reach a validated passing result.

Does spec-driven auto-coding work without manual git commits between tasks?

Spec-driven auto-coding uses commit-aware state tracking to persist task status and preserve completion state across cycles. This allows development to continue cleanly without manual intervention, ensuring progress is recorded after each validated implementation.

What are the limitations of automated test execution rounds in auto-coding workflows?

Automated test execution in this auto-coding workflow is limited to up to three auto-fix test rounds. If tests still fail after three iterative fix attempts, the process stops, requiring manual intervention to resolve persistent issues before progress can be persisted.