cycle

Orchestrate SpawnForge feature cycles from plan to validated implementation.

5|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Tristan578/project-forge --skill cycle-tristan578
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cycle
Source: https://github.com/Tristan578/project-forge/tree/main/.claude/skills/cycle
Command: npx skills add https://github.com/Tristan578/project-forge --skill cycle-tristan578

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a complete feature development lifecycle for SpawnForge by coordinating planner, builder, and validator to progress from specification to validated implementation.

Core Features & Use Cases

  • End-to-end lifecycle orchestration: Plan → Build → Verify → Update Context.
  • Phase gating and checks to ensure quality and consistency across the feature cycle.
  • Version-aware guidance and references to align across the Stack.

Quick Start

Provide a feature spec to the planner and trigger the end-to-end cycle from plan to verify.

Frequently Asked Questions about cycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate end-to-end feature delivery from specification to validation?

End-to-end feature delivery is orchestrated by aligning plan, build, and verify steps through a coordinated cycle. This process progresses from specification to validated implementation by enforcing phase sequencing and version constraints across planner, builder, and validator roles.

What is phase gating in an end-to-end development workflow?

Phase gating in an end-to-end development workflow enforces strict quality and consistency checks before advancing. It ensures the planner, builder, and validator complete their designated planning, coding, and testing phases in sequence before context updates occur.

How do I coordinate planning, coding, and testing phases for a new feature?

Planning, coding, and testing phases are coordinated by triggering an end-to-end cycle with a feature spec. The cycle aligns the planner, builder, and validator to sequentially process the specification, implementation, and verification stages.

Does the SpawnForge feature cycle enforce version constraints across the stack?

Yes, the SpawnForge feature cycle enforces version constraints and documented references to align across the stack. This version-aware guidance ensures features progress consistently from plan to verify without architectural misalignment.

Can I use this orchestration cycle for workflows outside of SpawnForge?

This orchestration cycle applies specifically to end-to-end development workflows for SpawnForge features. It coordinates the planner, builder, and validator using documented references and constraints aligned with the SpawnForge stack.

Why does my feature build fail validation during the end-to-end cycle?

Feature builds fail validation when phase sequencing checks detect misalignment between the plan, build, and verify steps. The cycle enforces strict quality gates, requiring documented references and version constraints to be satisfied before advancing.