architect-worker
Installation
SKILL.md
Architect & Worker Pattern
Separate software engineering responsibilities into two complementary agent roles synchronized through the workflow/ directory (spec-driven-workflow), optionally preceded and validated by the Product Owner role (product-owner):
- Product Owner (optional, via
product-owner) — Owns product intent, priority, and value validation throughworkflow/BACKLOG.md(the only root file inworkflow/) andworkflow/<change-slug>/VALIDATION.md. - Architect — Owns specifications, high-level architecture, execution planning, task sharding, code review, quality control, and delivery handoff inside
workflow/<change-slug>/. - Worker — Owns code implementation, testing, and remediation for a given
workflow/<change-slug>/, strictly following the Architect's specifications and all project documentation and skills.
Parallelism: Because each initiative lives in its own
workflow/<change-slug>/subdirectory, the Architect can specify and plan new items inworkflow/<other-slug>/while a Worker implements an already-ready plan inworkflow/<change-slug>/, and multiple Workers can execute non-conflicting plans concurrently.
Role Activation
- Explicit Role Assignment: Adopt the role specified by the user (e.g., "Act as the Architect" or "Act as the Worker", including equivalent role names in the user's language).
- Role Persistence: Maintain the assigned role for the entire session unless the user explicitly instructs a role switch.
- Missing Role Clarification: If this skill is invoked without a clear role assignment, ask the user whether to proceed as Architect or Worker before taking action.