development-lifecycle

Guide frontend React/TypeScript projects through gated lifecycle phases from planning to deployment.

3|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill development-lifecycle-malinskibeniamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development-lifecycle
Source: https://github.com/malinskibeniamin/skills/tree/main/development-lifecycle
Command: npx skills add https://github.com/malinskibeniamin/skills --skill development-lifecycle-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides frontend teams through a disciplined lifecycle from understanding to deployment.

Core Features & Use Cases

  • Spawns background agents to explore alternatives, prior art, and edge cases during planning
  • Enforces phased work: Understand -> Plan -> Grill -> Implement (TDD) -> Verify -> Ship
  • Includes gating and structured reviews (Grill, resilience checks, and /go flow) to ensure quality before shipping

Quick Start

Begin planning by entering Understand, then execute /ponytail full to lock a plan and keep it active through /go.

Frequently Asked Questions about development-lifecycle

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

FAQPage Schema
How do I structure a frontend lifecycle from planning to deployment?

Structure a frontend lifecycle using gated phases: Understand, Plan, Grill, Implement, Verify, and Ship. This enforces formal planning gates, grilling sessions, TDD cycles, and controlled shipping for disciplined project delivery.

What is a grilling session in frontend architecture planning?

A grilling session is a structured review gate during the planning phase. It spawns background agents to explore alternatives, prior art, and edge cases to ensure architecture resilience before implementation begins.

How do I apply TDD cycles to a React and TypeScript UI workflow?

Apply TDD cycles during the Implement phase of the gated workflow. This enforces test-driven development for React and TypeScript UI projects immediately after the Plan and Grill phases are locked.

Can I use this lifecycle workflow for non-React frontend projects?

The workflow applies to frontend projects requiring formal planning gates, especially React and TypeScript UI work. It enforces phased implementation, agent reviews, and resilience checks for any UI project.

How do I lock a plan and trigger deployment in a gated workflow?

Lock a plan by executing /ponytail full during the planning phase. Keep the plan active through the /go flow to transition from the Verify phase into controlled shipping and deployment.