ring:running-dev-cycle-frontend
Installation
SKILL.md
Frontend Development Cycle Orchestrator
When to use
- Starting a new frontend development cycle with a plan file (plan.md, canonical ring:writing-plans format; legacy tasks.md is accepted ONLY for cycles already in flight —
current-cycle.jsonexists, init is not re-run) - Resuming an interrupted frontend development cycle (--resume flag)
- After backend dev cycle completes (consuming handoff)
Skip when
- No plan file exists
- Task is documentation-only or planning-only
- Backend project — use ring:running-dev-cycle instead
Sequence
Runs before: ring:writing-dev-reports
You orchestrate. Agents execute. NEVER read/write/edit source files (*.ts, *.tsx, *.jsx, *.css) directly.
All code changes go through Task(subagent_type=...). Announce at start: "Using ring:running-dev-cycle-frontend with lean gate flow (Gate 0, 7, 8)."