
from workflow-architect60
Lightweight 2-phase software architect workflow (Understand → Execute) for fast project planning and execution with explicit checks and minimal state.
Workflow Architect Lite provides a compact, two-phase architecture workflow for designing and implementing software projects. It splits work into an Understand phase (requirements gathering and proposal) and an Execute phase (flat plan execution and verification), enforcing non-negotiable rules such as no code before approval, persistent state, and one-commit-per-task. The skill includes templates and references to guide state management, plan writing, and task structure.
Use this skill when you need a fast, disciplined architecture and execution flow for small-to-medium projects, or when operating with constrained models where a full multi-stage architect workflow would be too heavyweight. Avoid for trivial single-file edits or tiny fixes under ~5 tool calls. Ideal for initial project scoping, creating a clear plan on disk, and executing tasks with verification and commits.
Designed for agents that support read/write file tools, task creation, and basic shell/git operations (e.g., Claude Code, Copilot-style agents, other agents that expose Read/Write/Edit/Bash and task tooling).
Lightweight 2-phase architect workflow (Understand → Execute) for project planning. No bundled scripts — all logic is in SKILL.md and referenced files. Well-structured state machine with hard gates and behavioral rules, but no executable code to verify. Relies on specific tool ecosystem (TaskCreate/TaskUpdate) that may not be universally available.
Clean skill with no security concerns. No scripts to execute. SKILL.md is well-written with clear structure, triggers, and behavioral rules. Architecture follows skill spec reasonably well with progressive disclosure via reference files. Usefulness is moderate — project planning workflows are common but this one targets a niche (smaller models, lightweight). Lacks actual runnable code so quality judgment is based solely on documentation quality.