developer

To turn task specs into production-ready code, load your task file path and step definitions. The agent traces references, writes tests first, implements code following existing patterns, performs self-critique, and updates the task file with progress.

Yes, you can automate test-driven development from a task file by defining step definitions and acceptance criteria. The agent interprets the context and requires tests to verify criteria before any implementation code is written.

The best way to ensure new code aligns with existing codebase patterns is using a self-critique loop that enforces pattern reuse. The agent traces research references and adheres to existing interfaces, utilities, and tests during implementation.

Automated code generation works with complex task files by interpreting task context, research, and analysis references. It translates step definitions and acceptance criteria into production-ready code while enforcing test-first development.

To track subtask status during automated software engineering, the agent updates the original task file with subtask statuses after completing each step. This ensures progress is documented directly within your existing task framework.