story-to-production

Delivery workflow from approved story to release readiness

Metadados

phase: delivery
orchestrator: delivery-orchestrator
alias principal: /looply:story-to-production

Slash Command

command: /looply:story-to-production
argument hint: <feature-name> <story-reference> [constraints...]
hosts: codex, claude

Argumentos

feature-name required: short identifier for the feature in delivery
story-reference required: story to be delivered in this cycle
constraints optional, variadic: optional delivery notes, blockers or implementation constraints

Inputs

story
prd

Outputs

release-plan
operability-report

Stages

technical-design

task: create-tech-spec
agent: architect
inputs: story, prd
outputs: tech-spec

architecture-decision

task: create-adr
agent: architect
depends_on: technical-design
inputs: tech-spec
outputs: adr

implementation

task: implement-api
agent: backend
depends_on: technical-design, architecture-decision
inputs: tech-spec, adr
outputs: implementation-summary

technical-review

task: review-code
agent: reviewer
depends_on: implementation
inputs: implementation-summary
outputs: review-report

release-preparation

task: prepare-service-release
agent: devops
depends_on: technical-review
inputs: review-report, implementation-summary
outputs: release-plan

operability-review

task: assess-service-operability
agent: sre
depends_on: release-preparation, implementation
inputs: release-plan, implementation-summary
outputs: operability-report

Handoffs

architect -> backend via tech-spec
backend -> reviewer via implementation-summary
reviewer -> devops via review-report
devops -> sre via release-plan

Gates

design-approved after architecture-decision owner architect
implementation-reviewed after technical-review owner reviewer
release-ready after operability-review owner sre

Conteudo do artefato

Workflow: story-to-production

Objective

Executar delivery de uma story aprovada ate readiness de release com validacao operacional.

Orchestrator

delivery-orchestrator acompanha o estado da story, cobra gates tecnicos e decide o proximo especialista.

Execution

Usar backlog pronto como entrada e evitar misturar discovery com delivery.

Sequence

technical-design by architect
architecture-decision by architect
implementation by backend
technical-review by reviewer
release-preparation by devops
operability-review by sre

Quality Gates

design-approved bloqueia implementacao sem tech-spec e adr
implementation-reviewed bloqueia publicacao sem review-report
release-ready bloqueia encerramento sem release-plan e operability-report

Arquivo

packs/engineering-base/workflows/story-to-production.md

Voltar para workflows