An empty agent settings file, from a project described as: ReqForge — From requirements to shippable products. Open-source Agent Harness for Claude Code, Cursor & OpenCode. Spec→Plan→Build, hooks, review. /change-manager for brownfield.
Instructions for zxpmail/ReqForge, a project described as: ReqForge — From requirements to shippable products. Open-source Agent Harness for Claude Code, Cursor & OpenCode. Spec→Plan→Build, hooks, review. /change-manager for brownfield.
name: code-reviewer description: Dispatched by the main Agent when code review is needed. Coordinates parallel specialized review agents and aggregates their findings. skills: code-review model: opus color: red.
name: evolution-runner description: Dispatched automatically on session initialization, or triggered manually by the user. Uses the evolution-engine skill to scan feedback and generate evolution proposals. skills: evolution-engine model: opus color: purple.
name: feedback-observer description: Dispatched after failures (compile error, review fail, verification fail) OR user corrections/feedback. Auto-scores Skill dimensions on failure. Uses feedback-writer skill to record feedback. skills: feedback-writer model: opus color: blue.
name: implementer description: Dispatched when the project is large and the main Agent needs to split a Phase into independent Tasks for separate execution. Uses the dev-builder skill for coding, one fresh instance per Task. skills: dev-builder model: opus color: green.
name: planner description: Dispatched by the main Agent when development planning is needed. Uses the dev-planner skill to analyze Spec, split phases, and output DEV-PLAN.md. skills: dev-planner model: opus color: yellow.
name: test-writer description: Dispatched by the main Agent when automated tests are needed. Generates TypeScript test files for sync scripts and core utilities. skills: none model: sonnet color: yellow.
name: bug-fixer description: Used when the user says "this feature is broken", "getting an error", "something's not right", or reports a bug, compilation error, or runtime exception. Locates root cause through a four-stage systematic debugging process and fixes it. version: 1.2.0 updated: 2026-06-27 requires: [].
name: change-manager description: Used when the user adds a feature or incrementally changes an existing project that already has Product-Spec.md. Runs the changes/ workflow (propose, apply, verify, archive), aligned with OpenSpec-style SDD while delegating implementation to dev-planner and dev-builder. version: 1.1.0…
name: code-review description: Used when the user wants to review code, check quality, verify feature completeness, or needs to validate code implementation against Spec, DESIGN.md, and design mockups. Outputs a structured review report with evidence for each conclusion. version: 2.3.0 updated: 2026-07-16 requires: [].
name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…
name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…
name: dev-builder description: Used when DEV-PLAN.md is ready and the user says to start coding or continue developing the next Phase. Sets up the skeleton for new projects, implements features by Phase for existing projects. version: 1.2.0 updated: 2026-06-27 requires: [].