void-plan

Converts an approved spec into a vertical-slice implementation plan with TDD modes and verification gates.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-plan-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-plan
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-plan
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-plan-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Approved specs often stall because nobody defines the execution order, test discipline, or recovery points, so later sessions lose context and integration errors surface late. This Skill turns an approved spec into a concrete, on-disk plan that any session or agent can resume. ## Core Features & Use Cases - Vertical slice planning: Splits work into end-to-end slices (UI to persistence) with an explicit MVP-cut first, instead of horizontal phases that hide integration errors. - Per-step TDD mode and verification gates: Every implementation step declares strict, souple, or exploratory TDD mode plus an observable gate that must pass before the next step. - Resume point and execution handoff: Standalone plans carry a resume point for later sessions; multi-ticket programs get a dependency table handed off to tracker tooling. - Use Case: After brainstorm approves a checkout spec, invoke this Skill to produce docs/plans/2024-05-01-checkout-plan.md with eight gated steps, review checkpoints, and a resume point, then hand it to implementation. ## Quick Start Ask the agent to plan the approved spec at docs/specs/2024-05-01-checkout.md into vertical slices with TDD modes and verification gates.

Frequently Asked Questions about void-plan

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

FAQPage Schema
How do I turn an approved spec into an implementation plan?

Invoke the planning skill immediately after the spec is approved. It writes a markdown plan at docs/plans/ with a goal, numbered steps, verification gates, review checkpoints, and either a resume point or a tracker handoff table.

What is vertical slice planning versus horizontal phasing?

Vertical slicing cuts each step through all layers (UI, domain, persistence) so every step ships testable value. Horizontal phasing builds one layer at a time, which hides integration errors until the final wiring step.

Can I create a plan without an approved spec?

No. The skill explicitly refuses to plan without an approved spec, because planning without one means the brainstorm step was skipped. A spec with source: forge frontmatter counts as ready and can be consumed directly.

What TDD modes can each plan step declare?

Each implementation step declares strict, souple, or exploratory mode. Strict covers new business behavior and payment-surface changes, souple covers glue at integration boundaries, and exploratory covers spikes and throwaway scripts.

When should a plan be flagged as high risk?

Set high_risk: true when the plan touches payments, authentication, production data migrations, security-sensitive code, or LLM call sites with user input. This triggers a recommendation for a multi-lens plan review before execution.