Implementing Features

Spec-driven feature implementation automates the build process by linking active specifications to a multi-agent workflow. Provide a specification identifier—like '/quaestor:implement spec-feature-001'—and the system orchestrates discovery, planning, implementation, and validation phases across coordinated agents, enforcing quality gates every three edits.

Five specialized agents coordinate the workflow: a researcher gathers context, an architect designs the solution, a security agent reviews for vulnerabilities, an implementer writes code across files, and a QA agent validates against requirements. A workflow-coordinator manages handoffs and enforces mandatory planning approvals.

The four-phase workflow supports feature implementation, bug fixes with automated tests, and refactoring tasks. Each phase maintains language awareness across multi-file projects and applies the same quality gates and agent orchestration regardless of task type.

Planning approvals are mandatory gates in the workflow. If rejected, the system halts implementation and returns control for specification revision or constraint clarification before proceeding to the implementation phase.

Yes. The Skill integrates with .quaestor/specs and can reference both active and draft specifications. Link to any specification state when invoking the implementation command, and the system uses that specification as the source of truth for the entire workflow.

Documentation updates occur as a built-in step during implementation. The system synchronizes architecture docs and agent-specific documentation with code changes automatically, ensuring specifications, architecture decisions, and agent reasoning remain consistent.