Documents the dependency graph of /architect: commands, execution order, and estimated chain times
Prerequisite Graph Skill
Documents the complete dependency graph of the mapped /architect: commands (not yet exhaustive of all 63), showing which commands must run before others, in what order, with estimated execution times for full dependency chains.
Quick Reference: Command Dependency Tiers
Commands are organized by execution order:
Tier
Commands
ETA
Depends on
Tier 0: Foundation
blueprint, sdl, import
20-30 min
Nothing (can start empty)
Tier 1: Design & Schema
design-system, generate-data-model
15-30 min
Tier 0 complete
Tier 2: Code Generation
scaffold, scaffold-component
15-60 min
Tier 0, Tier 1
Tier 3: Development
implement, review, visualise
30 min - days
Tier 2 complete
Tier 4: Quality
generate-tests, security-scan
30-120 min
Tier 3 complete
Tier 5: Scale
load-test, setup-cicd, setup-monitoring
20-120 min
Tier 2 + Tier 4
Tier 6: Production
compliance, launch-check, production-readiness
60-180 min
Tier 5 complete
Tier 7: Growth
cost-estimate, technical-roadmap, etc.
15-45 min
Any tier (no strict dependency)
Full Dependency Graph
Tier 0: Foundation (Nothing required)
START
↓
blueprint — 20 min
├─ Problem validation (optional baseline)
├─ SDL generation (alternative to blueprint)
└─ Import existing project (alternative entry)
production-readiness requires: All above complete + compliance pass
Outputs:
Compliance audit report
Security remediation plan
Control implementation checklist
Launch readiness checklist
Production readiness score
Sign-off documentation
Exit criteria:
✅ All critical compliance controls addressed
✅ >80% test coverage
✅ Monitoring in place
✅ Disaster recovery plan documented
✅ Team trained and ready
Tier 7: Growth (no strict dependency, can run anytime)
Any prior tier complete
↓
cost-estimate — 15-30 min
└─ Estimate infrastructure costs
technical-roadmap — 30-45 min
└─ Plan scaling and feature roadmap
user-journeys — 20-30 min
└─ Map user workflows and pain points
user-personas — 20-30 min
└─ Define target users and characteristics
deep-research — 30-60 min
└─ Market research, competitor analysis
mvp-scope — 20-30 min
└─ Define MVP scope vs. later phases
problem-validation — 30-60 min
└─ Validate market problem
generate-docs — 30-90 min
└─ Generate full documentation suite
pitch-deck — 30-60 min
└─ Generate investor pitch deck
hiring-brief — 20-30 min
└─ Create hiring guide for new team members
Dependencies:
No strict dependencies
Can run in any order
Outputs used for planning, analysis, documentation
Path A (above) — 7-14 days
↓
setup-cicd (25 min)
↓
setup-monitoring (40 min)
↓
security-scan (30 min)
↓
compliance (90 min)
↓
launch-check (15 min)
↓
production-readiness (45 min)
↓
READY FOR PRODUCTION (9-17 days total)
Path C: Enterprise-Ready (All hardening)
Path B (above) — 9-17 days
↓
load-test (60 min)
↓
accessibility-audit (30 min)
↓
technical-roadmap (30 min)
↓
disaster-recovery (60 min)
↓
READY FOR ENTERPRISE (11-19 days total)
Dependency Rules
Hard Dependencies (blocking)
Some commands cannot start until other commands complete:
scaffold ⚠️ requires design-system + generate-data-model
└─ Cannot generate code without design tokens or schema
generate-tests ⚠️ requires scaffold
└─ Cannot test code that doesn't exist
setup-monitoring ⚠️ requires scaffold
└─ Cannot monitor services that don't exist
production-readiness ⚠️ requires generate-tests + setup-monitoring + compliance
└─ Cannot launch without safety gates
Soft Dependencies (recommended but not blocking)
Some commands work better with other commands completed, but don't strictly require them:
generate-tests ✓ works better after blueprint
└─ Can test without blueprint context, but tests are more meaningful with architecture context
cost-estimate ✓ works better after scaffold
└─ Can estimate based on blueprint alone, but better with actual component count
technical-roadmap ✓ works better after implement
└─ Can plan without implementation, but roadmap more accurate with progress
Optional Dependencies
Some commands have no dependencies:
blueprint — can run on empty project
sdl — can generate schema from nothing
user-personas — can define without any code
problem-validation — can validate without system
Parallel Execution Opportunities
Some commands can run in parallel (no dependency relationship):
Parallel Safe:
┌─ design-system (15 min)
│
blueprint (20 min) ┤
│
└─ generate-data-model (20 min)
All three can run together, save ~25 minutes vs. sequential
Actual time: max(20, 15, 20) = 20 min instead of 20+15+20 = 55 min
Another parallel opportunity:
┌─ generate-tests (120 min)
│
scaffold (45 min) ┤─ implement (N days)
│
└─ setup-cicd (25 min)
After scaffold completes, tests + cicd can run in parallel during implement
Dependency Matrix
Quick lookup of what each command requires:
Command
Requires
Optional
Tier
blueprint
—
problem-validation
0
sdl
—
blueprint
0
import
existing codebase
—
0
problem-validation
—
—
0
design-system
blueprint
—
1
generate-data-model
SDL entities
—
1
user-personas
—
problem-validation
1
deep-research
—
—
7
mvp-scope
blueprint
—
7
scaffold
blueprint, design-system, generate-data-model
—
2
scaffold-component
scaffold
—
2
implement
scaffold
blueprint
3
visualise
blueprint, scaffold
—
3
review
scaffold, code
—
3
generate-tests
scaffold
blueprint
4
security-scan
scaffold
—
4
accessibility-audit
scaffold
—
4
setup-cicd
scaffold
—
5
setup-monitoring
scaffold
—
5
load-test
scaffold
—
5
compliance
scaffold
security-scan
6
launch-check
scaffold, tests, monitoring
—
6
production-readiness
tests, monitoring, compliance
—
6
cost-estimate
blueprint
scaffold
7
technical-roadmap
blueprint
—
7
user-journeys
—
mvp-scope
7
pitch-deck
—
user-personas
7
wireframes
design-system
—
7
prototype
scaffold
design-system
7
prototype-iterate
prototype
—
7
sync-backlog
—
—
7
agent-spec
—
—
7
check-env
scaffold
—
7
publish-api-docs
scaffold
contracts
7
validate-consistency
— (any project state)
—
7
next-steps
— (any project state)
—
7
check-state
— (any project state)
—
7
launch-checklist
blueprint
—
7
onboarding-pack
—
—
7
hiring-brief
blueprint
—
7
compare-stack
—
—
7
complexity-check
blueprint
—
7
well-architected
blueprint
—
7
database-scaling
generate-data-model
—
7
seo
scaffold
—
7
analytics-setup
scaffold
—
7
disaster-recovery
production-readiness
setup-monitoring
6
i18n-setup
scaffold
—
7
setup-env
scaffold
—
7
export-diagrams
visualise
—
7
quick-spec
—
—
7
sprint-status
— (in-conversation)
—
7
Estimated Total Runtimes
By project goal:
Goal
Critical Path
Total Time
Commands
Concept Phase
problem-validation
30 min
1-2
MVP Ready
Tier 0-3
7-14 days
5-7
Launchable
Tier 0-6
9-17 days
10-14
Enterprise-Ready
Tier 0-7
11-20 days
20-25
Full Scope
All mapped commands
30-60 days
—
Note: Actual time depends heavily on implement duration (days to months).
Using This Graph
For /architect:next-steps
Use the prerequisite graph to:
Score commands — give higher scores to unblocked commands in critical path
Calculate ETAs — show total time from current state to launch
Show blockers — explain why a high-value command is blocked
For /architect:validate-consistency
Use the graph to:
Detect cascading failures — if Tier 2 command failed, warn about Tier 3+ being at risk
Recommend rerunning prerequisites — if Tier 2 is stale, suggest rerun before Tier 3
For /architect:production-readiness
Use the graph to:
Check all required commands complete — verify Path B (Launch-Ready) is done
Block launch if gaps — if any Tier 0-6 command missing, fail gate
For Users Planning Work
Use the graph to:
Understand sequencing — see which commands must run before others
Estimate timeline — pick a critical path and estimate days/hours
Identify parallelization — find commands that can run together
Updating the Graph
When a new command is added to the plugin:
Identify tier: Where does it fit (foundation, design, code gen, etc.)?
List dependencies: What must exist before this command runs?
Estimate time: How long does it take (include I/O time)?
Update diagram: Add to tier section and dependency matrix
Update critical paths: Does this change MVP or launch timelines?
Related Documentation
/architect:next-steps — uses graph to recommend commands
/architect:check-state — validates state from completed commands
/architect:validate-consistency — detects when prerequisites are incomplete
blocker-detection/SKILL.md — identifies specific blockers
stage-detection/SKILL.md — uses graph to understand project progression