aid-development
FreeAID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
The English summary is being prepared. Showing the original description.
Automatic quality check on significant outputs via isolated sub-agent. Spawns reflection-agent for objective evaluation without conversation context bias.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Apply (spawn agent): code, architecture, PRD, specs, tests, plans, APIs, schemas. Skip: simple questions, status checks, file reading, clarifying questions, help.
The sub-agent gets NO conversation context. It evaluates purely on merit — inline evaluation shares your context, agrees with your reasoning, and trends to 10/10. The agent sees only output + request + WHY, and can verify claims in source files.
Extract these for the agent. Do NOT summarize or add context.
| Variable | How to Extract |
|---|---|
{{ORIGINAL_REQUEST}} | First user message that initiated this task - VERBATIM |
{{STATED_WHY}} | The WHY established at conversation start - EXACT TEXT |
{{PHASE_NUMBER}} | Read from .aid/state.json → current_phase |
{{PHASE_NAME}} | Read from .aid/state.json → phase_name |
{{OUTPUT_TO_EVALUATE}} | Your draft output (code, spec, etc.) |
{{FILES_TO_VERIFY}} | Read content of all files your output references/modifies |
{{PHASE_CRITERIA}} | Read from criteria/phase-{N}-{name}.yaml |
DO: copy original request exactly as user wrote it; copy stated WHY exactly as established; include ALL files the output references (not just some); load criteria from the YAML file.
DO NOT: ❌ summarize the request; ❌ explain your decisions; ❌ include conversation history; ❌ mention previous attempts; ❌ add "helpful context".
Task(
subagent_type: "general-purpose",
model: "opus",
prompt: [Load ../../agents/reflection-agent.md, replace variables],
description: "Objective quality evaluation"
)
After receiving agent response, display:
╭─────────────────────────────────────────────────────────────╮
│ 🔍 Quality Check │
├─────────────────────────────────────────────────────────────┤
│ │
│ [icon] WHY Alignment X/10 [agent's note] │
│ [icon] Phase Compliance X/10 [agent's note] │
│ [icon] Correctness X/10 [agent's note] │
│ [icon] Security X/10 [agent's note] │
│ [icon] Completeness X/10 [agent's note] │
│ │
│ ══════════════════════════════════════════════════════ │
│ 📊 Overall: X.X/10 │
│ STATUS: [agent's status] │
│ │
│ [If revised: 📝 Improvements: ...] │
│ │
╰─────────────────────────────────────────────────────────────╯
| Score | Icon |
|---|---|
| 8-10 | ✅ |
| 6-7.9 | ⚠️ |
| 0-5.9 | ❌ |
If agent returns pass: false:
revision_guidance.required_changes"Security 5→8/10 Fixed: Added input validation"On project load or /good-morning, spawn session review instead:
Task(
subagent_type: "general-purpose",
model: "opus",
prompt: [Load ../../agents/reflection-agent.md],
description: "Session review - outside perspective"
)
Session review variables:
{{STATE_JSON}} - Content of .aid/state.json{{CONTEXT_JSON}} - Content of .aid/context.json{{RECENT_CHANGES}} - Output of git log --oneline -10{{RECENT_FILES}} - Output of git diff --stat HEAD~5{{PHASE_CRITERIA}} - Current phase criteria YAML| Command | Action |
|---|---|
/reflect | Show detailed breakdown of last evaluation |
/reflect --session | Run session review |
/reflect --strict | Run evaluation with threshold 8.0 |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
The English summary is being prepared. Showing the original description.
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
The English summary is being prepared. Showing the original description.
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
The English summary is being prepared. Showing the original description.
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
The English summary is being prepared. Showing the original description.
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
The English summary is being prepared. Showing the original description.
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
The English summary is being prepared. Showing the original description.