Spec to Pull Request

Anatomy

What it contains

• An ordered set of phases
• Agents, skills, commands, or scripts used by each phase
• Inputs, outputs, gates, and stop conditions

Lifecycle

How it works

1. The workflow validates its input
2. Each phase produces an explicit artifact
3. Gates decide whether the next phase may begin
4. The final phase verifies the requested outcome

Audit lens

What Zebonastic would check

• Every phase has bounded authority
• Artifacts and state transitions are inspectable
• Failure, retry, and rollback behavior are defined

Content preview

Workflow script

export default {
  name: "release-readiness",
  phases: [
    { name: "quality", run: ["lint", "test"] },
    { name: "review", agents: ["code-reviewer", "security-auditor"] },
    { name: "release", requires: ["quality:pass", "review:pass"] }
  ]
}

Related

More Workflows