planning

Generate design documents with a 4-stage convergence review loop.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/4armsxlr8/ccx-arsenal --skill planning-4armsxlr8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/4armsxlr8/ccx-arsenal/tree/main/plugins/agent-core/skills/planning
Command: npx skills add https://github.com/4armsxlr8/ccx-arsenal --skill planning-4armsxlr8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive approach to application development by generating design documents through a 4-stage convergence review loop, eliminating the need for manual ticket creation and enabling lazy materialization.

Core Features & Use Cases

  • 4-Stage Convergence Loop: Generates KPIs, Specifications, Stories, and UI Screens in a structured loop.
  • Lazy Materialization: Creates tickets lazily based on Sprint Contracts, reducing manual overhead.
  • Use Case: Ideal for teams looking to streamline the application development process from user requirements to final UI screens.

Quick Start

Use the planning skill to generate a design document for your application 'my_app'.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I generate a design document for application development from user requirements?

To generate a design document for application development, you input structured user requirements into the planning skill, which processes them through a 4-stage convergence review loop to produce KPIs, specifications, stories, and UI screens.

What is a convergence review loop in UI design and storyboarding?

A convergence review loop in UI design and storyboarding is an iterative 4-stage process that successively refines KPIs, specifications, stories, and UI screens to ensure application development aligns with user requirements.

How does lazy ticket creation work based on Sprint Contracts?

Lazy ticket creation based on Sprint Contracts defers materializing development tickets until necessary, reducing manual overhead by generating them directly from the defined stories and UI screens.

What format should structured user requirements take for generating application design documents?

Generating application design documents requires structured user requirements that define your application goals, enabling the convergence review loop to accurately output KPIs, specifications, and storyboards.

Can I streamline application development without manual ticket creation?

You can streamline application development without manual ticket creation by using the planning skill's lazy materialization feature, which automatically generates tickets based on Sprint Contracts.

Does this application development skill support standalone UI design and storyboarding?

The skill supports UI design and storyboarding as integral stages within its 4-stage convergence review loop, generating these elements sequentially after KPI definition and specification rather than as isolated standalone tasks.