gsd

Spec-driven development workflows are coordinated through phase-based commands for planning, execution, verification, and documentation. You initialize a project, then sequentially apply plan, execute, verify, and document commands to enforce structured, deterministic agent interactions with clear guardrails.

Multi-phase projects using Hermes agents are managed by applying phase-based commands sequentially. You start a project with an initialization command, then use specific plan and execute commands for each numbered phase to orchestrate agent workflows deterministically.

Yes, compressed communication inspired by caveman syntax reduces token usage during project planning and execution without sacrificing technical precision. This approach is integrated directly into the agent interactions to maintain deterministic outputs.

Spec-driven development for Hermes agents enforces a YAML frontmatter entry point for deterministic interactions. This defined structure ensures clear guardrails and consistent command processing across the planning, execution, and verification phases.

To start a multi-phase project, you run the new project initialization command. After initialization, you plan the first phase using a specific phase-planning command, then trigger the execution command for that phase number to begin agent orchestration.

Phase-based command orchestration relies on deterministic interactions and strict guardrails, meaning workflows must follow the defined plan, execute, verify, and document sequence. Deviating from this structured spec-driven process may break the deterministic agent coordination.