convergence-outline

Plan vertical feature outlines with phases, files, signatures, and checkpoints.

2|Updated Mar 31, 2026

Search Tags:#architecture #verification #outline #software #vertical-slice #phase-planning #feature-design

Ready to run

npx skills add https://github.com/c-sonnier/convergence --skill convergence-outline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convergence-outline
Source: https://github.com/c-sonnier/convergence/tree/main/plugins/convergence/skills/outline
Command: npx skills add https://github.com/c-sonnier/convergence --skill convergence-outline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces a concise, end-to-end vertical-slice plan that guides multi-phase feature development, ensuring testable progress and clear handoffs between design, implementation, and verification.

Core Features & Use Cases

Enforces vertical slices that touch all required layers (model, service, controller, and view) per phase.
Specifies per-phase artifacts: files to change, new type signatures, and verification checkpoints.
Provides a compact human-review step to validate phase order and structure before implementation.

Quick Start

Run the outline writer after design approval to produce a concise vertical-slice plan detailing phases, files to change, new signatures, and verification checkpoints.

Frequently Asked Questions about convergence-outline

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

FAQPage Schema

How do I plan a vertical slice feature outline with testable phases?▼

A vertical slice outline breaks feature development into testable phases that touch all required layers, including model, service, controller, and view. It specifies files to change, new signatures, and verification checkpoints per phase to ensure clear handoffs.

When do I need an end-to-end feature outline for software architecture?▼

You need an end-to-end feature outline when planning multi-phase feature development after design approval. It guides teams in aligning on phase boundaries, required changes, and verification steps before implementation begins.

What is the best way to structure feature phase planning for multi-phase development?▼

The best way to structure feature phase planning is by enforcing vertical slices that touch all required layers per phase. This structure provides per-phase artifacts including files to change, new type signatures, and verification checkpoints.

Does this vertical slice planning approach require design approval first?▼

Yes, this vertical slice planning approach requires convergence-design approval first. It is intended for multi-phase features after design approval to help teams align on phase boundaries and required changes before implementation.

How do I verify implementation checkpoints across feature phases?▼

To verify implementation checkpoints across feature phases, the outline specifies verification steps for each phase. This ensures testable progress and clear handoffs between design, implementation, and verification throughout development.

What artifacts are specified per phase in a vertical slice outline?▼

The artifacts specified per phase in a vertical slice outline include files to change, new type signatures, and verification checkpoints. These artifacts ensure testable progress and clear handoffs between design, implementation, and verification.