ada-agent-assisted-development

Orchestrates phased software development workflows with sub-agent reviews and context management.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-agent-assisted-development-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-agent-assisted-development
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-agent-assisted-development
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-agent-assisted-development-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long agent sessions degrade: analysis, implementation, and review blur together in one context, causing self-review blindness, bundled fixes, and the fix-break-fix spiral. This Skill structures software work into phased workflows with fresh contexts and independent sub-agent verification. ## Core Features & Use Cases - Seven End-to-End Workflows: Bug fix, feature implementation, code review, code quality optimization, architecture upgrade, SRS coverage analysis, and quality reporting, all following an Understand → Plan → Execute → Review → Report pattern. - Sub-Agent Isolation Rules: Reviewer never equals implementer, fixer never equals reviewer, and auto-fix retries are capped at 2 cycles before escalation. - Context Hygiene Discipline: Explicit rules for when to reset context (/new, /compress, delegate_task) plus a Rule of Three escape hatch when repeated fixes fail. - Use Case: A developer reports a bug; the agent first reproduces it with a failing test, traces the root cause, applies a minimal fix, then delegates an independent sub-agent review and verifies every claim by re-running tests before reporting. ## Quick Start Ask the agent to fix a bug using the structured workflow: reproduce it with a failing test first, analyze the root cause, apply a minimal fix, then run an independent sub-agent review.

Frequently Asked Questions about ada-agent-assisted-development

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

FAQPage Schema
How do I structure an AI agent bug fix workflow?

Follow the five-step pipeline: reproduce the bug with a failing test, analyze the root cause without changing code, apply a minimal fix, delegate an independent sub-agent review, then verify all claims by re-running tests. Never skip reproduction or let the implementer self-review.

How to use sub-agents for independent code review?

Use delegate_task to spawn a fresh-context sub-agent that receives only the diff, never the implementation reasoning. The reviewer must never be the implementer, and the fixer must be a separate sub-agent from the reviewer.

When should I reset an AI agent's context during development?

Reset context when moving from analysis to implementation, before any review phase, after a failed approach, or when the session exceeds roughly 50 turns. Use /new for full resets, /compress for long sessions, and delegate_task for isolated sub-tasks.

What is the Rule of Three in agent-assisted debugging?

If three consecutive fix attempts fail for the same bug, stop fixing and question the architecture instead. This is the escape hatch from the fix-break-fix-break spiral where repeated patches treat symptoms rather than root causes.

When should I not use structured agent workflows?

Skip these workflows for single isolated tool calls, throwaway experiments with no verification requirements, or work that fits in one session without context resets. The overhead of phased orchestration only pays off on multi-step, verifiable tasks.