Process: Build Priority Review

Process: Build Priority Review

Owner: CTO (Clara) Type: Manual + Agent-assisted Frequency: At phase transitions and when blockers arise

Purpose

Ensures the factory build order remains optimal — roles are built in the right sequence, blockers are identified early, and adjustments are communicated when priorities shift.

Steps

1. Review current phase progress

  • Read company/org-chart.md for the build order and phase plan
  • Check the STATUS.md (if it exists) for current build status
  • Scan departments/ to see which roles have been fully built (role.md + agent.md + commands + processes)
  • Identify which roles in the current phase are complete, in progress, or not started

Output: Phase progress snapshot.

2. Identify blockers

Look for:

  • Dependency blockers: A role that should be built next depends on an incomplete role
  • Technical blockers: A technical question or decision is blocking progress
  • Resource blockers: Too many roles in flight, or a critical path role is stalled
  • Scope creep: Work on future-phase items happening before current phase is done

Output: List of blockers with severity (critical / moderate / low).

3. Adjust ordering if needed

When blockers require a change:

  • Evaluate whether the build order can be resequenced without breaking dependencies
  • Consider whether a role can be partially built (role.md only) to unblock others
  • If a phase is nearly complete, consider starting the next phase's critical-path items
  • Never skip a dependency — adjust the order, don't skip steps

Output: Updated priority recommendation (if changes needed).

4. Communicate changes

  • Report findings to the CEO (founder)
  • If the build order changes, document the rationale
  • Update affected roles on new timelines or dependencies
  • If no changes are needed, confirm the current plan is on track

Output: Communication to stakeholders.

Build order reference

From org-chart.md Phase 1:

Order Role Depends on
1 Infrastructure Engineer Nothing — foundation
2 Methodology/Nomenclature Specialist #1 (needs repo structure)
3 CTO #1, #2 (needs structure and standards)
4 Enterprise Architect #2, #3 (needs standards and tech direction)
5 Agentic Pattern Designer #4 (needs architecture blueprint)

Quality gate

A build priority review is complete when:

  • Current phase progress is documented
  • All blockers are identified and categorized
  • Recommendations are actionable and respect dependencies
  • Changes (if any) are communicated to affected roles