agentic-dev

Agentic Development Workflow

A structured, 5-phase framework for building software with AI coding agents. Gives LLMs clear specifications, atomic tasks, and role-matched expertise — so you get predictable, high-quality output instead of hoping the AI figures it out.

Note: I created this project to better understand agentic software development methodology. There may be a bunch of stupid stuff here. For real projects, check out Superpowers, GSD, Spec Kit, EPCC, oh-my-claudecode, Compound Engineering, Agent Skills and incorporate whatever works for you.

The Problem

Most people use AI coding tools by throwing a vague prompt at an LLM and hoping for the best. This works for small tasks but falls apart for anything real:

• The AI makes assumptions instead of asking
• Specifications live in your head, not in documents the AI can read
• Tasks are too big, so context degrades and quality drops
• No verification — you merge code you haven't meaningfully reviewed
• Knowledge is lost between sessions

How This Helps

This workflow breaks AI-assisted development into 5 phases with human gates between each:

Phase 1        Phase 2          Phase 3           Phase 4         Phase 5
Research  -->  Specification  -->  Task Breakdown  -->  Execution  -->  Verification
          [GATE]             [GATE]               [GATE]          [GATE]

Phase 1: Research — Human gathers materials, AI performs deep research to fill gaps and cross-reference findings.

Phase 2: Specification — AI generates architecture specs (SPEC.md) with milestones, schemas, API contracts, and diagrams. No code. Optional multi-role review (security, domain, product).

Phase 3: Task Breakdown — Spec is decomposed into atomic tasks grouped into parallel waves, with role assignments and test separation.

Phase 4: Execution — One task per session, role-matched agents, automated verification, human review via task review files, PR on approval.

Phase 5: Verification — Per-milestone end-to-end testing and retrospective.

Each phase produces persistent documents (SPEC.md, PLAN.md, PROGRESS.md, decision records, task reviews) that survive across sessions and prevent context rot.

What's Included

Component	Count	Description
Skills	8	init-project, research, spec, plan, execute, review, verify, auto
Agents	13	Software Architect, Backend Engineer, QA Engineer, Security Reviewer, and more

Installation

Claude Code Plugin (recommended)

# Add the marketplace
/plugin marketplace add wilsonkichoi/agentic_development_workflow

# Install the plugin — select "Install for you, in this repo only (local scope)"
/plugin install agentic-dev@wilsonkichoi-agentic-dev

When prompted for install scope, choose "Install for you, in this repo only" (local scope). This keeps the plugin scoped to your project rather than applying globally, which is recommended while the workflow is still evolving.

After installation:

• Skills are available as /agentic-dev:research, /agentic-dev:spec, etc.
• Agents appear in /agents (e.g., agentic-dev:backend-engineer)
• Auto-updates when the repo is updated

Copilot CLI

copilot plugin install wilsonkichoi/agentic_development_workflow

After installation:

• Skills are available as /init-project, /research, /spec, /plan, /execute, /review, /verify, /auto
• Agents appear in /agent (e.g., backend-engineer, qa-engineer)
• Plugins install globally to ~/.copilot/state/installed-plugins/

Note: Copilot CLI does not support per-project plugin scoping. Installed plugins are always global — there is no --scope flag or disable/enable per workspace (unlike Gemini CLI). If you need project-level control, use Claude Code's local scope install or Gemini CLI's workspace scope instead.

Gemini CLI

To avoid polluting the global context, install the extension globally but keep it disabled by default. Enable it strictly on a per-workspace basis:

# 1. Install the extension from GitHub
gemini extensions install https://github.com/wilsonkichoi/agentic_development_workflow

# 2. Disable the extension globally (user scope) so it doesn't pollute all your projects
gemini extensions disable agentic-development-workflow --scope user

# 3. Navigate into specific projects and enable it locally (workspace scope)
cd /path/to/your-project
gemini extensions enable agentic-development-workflow --scope workspace