HarnessCommunity★ 500

AgenticDev (git-workflow)

Updated Jul 7, 2026

AgenticDev is a modular spec-driven development methodology by bodangren implemented as Claude Code skills. Four phases: Discovery & Planning (prd-authoring, spec-authoring), Organization (sprint-planner decomposes specs into GitHub Issues), Execution (issue-executor implements each issue via TDD with a repro-first loop; sprint-manager coordinates), and Integration (change-integrator promotes specs, updates the retrospective, and closes issues).

View on GitHub

What it does

prd-authoring
Generates Product Briefs, Research Plans, and full PRDs from initial ideas using AI.
spec-authoring
Manages the Spec PR workflow: drafts a detailed technical specification and analyzes PR review feedback before approval.
sprint-planner
Decomposes an approved spec into atomic GitHub Issues with acceptance criteria and organizes them into a milestone.
issue-executor
Implements a single GitHub Issue via a TDD repro-first loop: create repro script → make it fail → implement fix → verify it passes.
sprint-manager
Orchestrates an entire sprint by coordinating issue-executor sub-agents serially through all milestone issues.
change-integrator
Post-merge cleanup: promotes spec to approved, auto-summarizes learnings into RETROSPECTIVE.md, and closes related issues.

Files (1)

OVERVIEW.mdprimary · markdown · 2.2 KB

## What it does

AgenticDev (github.com/bodangren/git-workflow) is a modular spec-driven development methodology implemented as Claude Code skills. The core principle is "think before you code" — every feature starts with a written spec that must be approved before sprint planning begins.

12 skills in the catalog:

- project-init — scaffolds docs/specs/ and docs/changes/ directory structure
- project-migrate — AI-powered migration of existing brownfield projects into the AgenticDev structure
- prd-authoring — generates Product Briefs, Research Plans, and full PRDs from initial ideas
- spec-authoring — manages the Spec PR workflow (draft spec → PR → review → approval)
- doc-indexer — scans project docs and produces a just-in-time frontmatter context map for agents
- doc-validator — enforces documentation standards and catches files in wrong locations
- sprint-planner — decomposes an approved spec (epic) into atomic GitHub Issues with a milestone
- sprint-manager — orchestrates a full sprint by coordinating issue-executor sub-agents serially
- issue-executor — the core workhorse: loads context, creates a TDD plan (Repro → Fix → Verify), opens a feature branch, implements, and manages the fix loop
- change-integrator — post-merge cleanup: promotes spec to "approved," auto-summarizes learnings into RETROSPECTIVE.md, closes issues
- agent-integrator — keeps AGENTS.md updated as new skills are added
- frontend-design — specialized skill for UI/UX tasks and frontend component design

## Install

    # New project
    bash skills/project-init/scripts/init-project.sh
    bash skills/agent-integrator/scripts/update-agents-file.sh

    # Existing project
    bash skills/project-migrate/scripts/project-migrate.sh

## When to use

Works best when you want GitHub Issues as the coordination artifact — each issue maps to a TDD implementation cycle, and the milestone gives a clear progress view. The repro-first approach in issue-executor is particularly effective for bug fixes: write a script that reproduces the failure before touching the fix, then verify the script passes after. The RETROSPECTIVE.md accumulates learnings across sprints automatically.