gds-quick-dev

Implements code changes through a spec-driven plan, implement, and adversarial review workflow.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-quick-dev-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-quick-dev
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-quick-dev
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-quick-dev-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature request or bug fix into reviewed, working code usually requires ad-hoc planning, manual code review, and untracked scope creep. This Skill structures that entire cycle: it clarifies intent, writes a bounded specification, implements the change, runs multi-agent adversarial review, and produces a human-reviewable diff trail. ## Core Features & Use Cases - Spec-driven development: Generates a token-bounded spec (900–1600 tokens) with intent, boundaries, I/O edge-case matrix, tasks, and acceptance criteria before any code is written. - Dual routing: Chooses between a one-shot path for zero-blast-radius changes and a full plan-code-review path for everything else. - Adversarial review loop: Launches blind, edge-case, and acceptance-auditor review subagents, classifies findings (intent_gap, bad_spec, patch, defer, reject), and loops back to re-derive code when needed. - Epic context compilation: Distills PRD, architecture, and UX planning documents into a focused per-epic context file, and syncs story status with sprint-status.yaml. - Use Case: Ask it to "add pagination to the orders API" and it will investigate the codebase, draft a spec for your approval, implement the change, run three independent reviews, fix findings, commit, and open a clickable Suggested Review Order in your editor. ## Quick Start Ask the agent to implement a feature or fix a bug, for example: implement user session timeout handling following the project's existing patterns.

Frequently Asked Questions about gds-quick-dev

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

FAQPage Schema
How do I implement a feature with a spec-driven AI workflow?

Describe your intent in plain language and the workflow clarifies it, investigates the codebase, and writes a bounded specification for your approval before coding. After you approve, it implements the change, runs adversarial reviews, and commits with a review trail.

How does the adversarial code review process work?

Three subagents review the diff independently: a blind hunter with only the diff, an edge case hunter with project access, and an acceptance auditor checking the spec. Findings are classified as intent gaps, spec flaws, patches, deferrals, or noise, with loopbacks for serious issues.

When does the workflow choose one-shot versus plan-code-review?

One-shot is chosen only when the change has zero blast radius with clear intent and no architectural decisions. Everything else, including any uncertainty about side effects, routes to the full plan-code-review path with spec approval and multi-agent review.

Can it work with epics and sprint status tracking?

Yes. For epic stories it compiles a focused epic context file from planning artifacts and syncs story status in sprint-status.yaml, lifting parent epics from backlog to in-progress automatically. Freeform work skips sprint sync entirely.

What happens if my runtime cannot spawn subagents?

The workflow writes review prompt files to the implementation artifacts directory and halts, asking you to run each review in a separate session and paste back findings. Epic context compilation also falls back to inline execution.

Why does the workflow halt and ask questions during planning?

It halts when intent is ambiguous, the spec exceeds 1600 tokens, multiple independent goals are detected, or the git working tree is dirty. These checkpoints prevent hallucinated requirements and scope creep before code is written.