Some checks failed
validation / verify (push) Failing after 10s
A new Deliverable in the packaging Phase, produced by a delivery planner after validation. - The planner writes the plan as data: work packages that name the Elements they deliver, and activities with days, what each follows, and whether the team or the customer owns it. - Code checks the plan against the design: every Element belongs to a work package, and the activities can be scheduled. - Code computes the schedule, with no more of the team's activities at once than the team has people, and the critical path. - Code writes the WBS dictionary (a work package is done when the Checks on its Elements pass), the activity sequence and a timeline on a relative axis from Day 0. - The plan is checked against the delivery window from the agreed scope; over it, the Deliverable says by how much and names the critical path. - With a start date it also gives calendar dates and a Mermaid Gantt chart. - The timeline is added to the solution guide, and the plan's length is in execution.json and the packaging Approval. Not run with real models. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
53 lines
2.0 KiB
YAML
53 lines
2.0 KiB
YAML
name: gcp-solution-architecture-workflow
|
|
source_template: https://github.com/workflow_agent/template
|
|
repository: gcp_solution_architecture_agent
|
|
# Phases and their Deliverables mirror app/workflows/deliverables.py, the single source
|
|
# for the dependency graph. A Phase completes when every Deliverable is submitted and the
|
|
# user grants its Approval. Outputs are written to deliverables/executions/<execution_id>/.
|
|
phases:
|
|
- id: scoping
|
|
input: [workflow_request, scope_spec]
|
|
deliverables: [scope]
|
|
attachments: [scope.yaml, scope.json]
|
|
approval: required
|
|
- id: requirements_discovery
|
|
input: scope
|
|
deliverables: [requirements, technical_decomposition]
|
|
product_selection_deferred: true
|
|
approval: required
|
|
- id: solution_architecture
|
|
input: [requirements, technical_decomposition]
|
|
deliverables:
|
|
- product_selection
|
|
- design_recommendations
|
|
- target_architecture
|
|
attachments: [target-architecture.json, architecture.mmd]
|
|
approval: required # the Target architecture is approved before any code is written
|
|
- id: solution_implementation
|
|
input: [target_architecture]
|
|
deliverables:
|
|
- architecture_description
|
|
- deployment_guidance
|
|
attachments: [terraform/main.tf, terraform/variables.tf, implementation.json]
|
|
approval: required
|
|
- id: solution_validation
|
|
input: [deployment_guidance]
|
|
deliverables: [validation_results]
|
|
deploy_resources: false
|
|
approval: required
|
|
- id: packaging
|
|
input: [validation_results]
|
|
deliverables: [work_breakdown, solution_guide]
|
|
attachments: [work-breakdown.json]
|
|
output: solution-architecture-guide.md
|
|
approval: required
|
|
verification:
|
|
- step: 4
|
|
check: solution-architecture-guide.md exists and is non-empty
|
|
- step: 5
|
|
check: workflow.yaml covers the five Phases and required artifacts exist
|
|
- step: 6
|
|
check: committed revision is published
|
|
- step: 7
|
|
check: remote revision contains workflow.yaml and solution-architecture-guide.md
|