prevc-planning

Automate idea validation into specs and test-first implementation plans.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/NEXUZ-SYS/devflow --skill prevc-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prevc-planning
Source: https://github.com/NEXUZ-SYS/devflow/tree/main/skills/prevc-planning
Command: npx skills add https://github.com/NEXUZ-SYS/devflow --skill prevc-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PREVC Planning phase requires structured, evidence-based translation of ideas into validated specs and implementation roadmaps, which this skill provides by coordinating Socratic brainstorming with context enrichment and formal scaffolding.

Core Features & Use Cases

  • 9-step Socratic brainstorming with structured QA and design exploration
  • Context enrichment via dotcontext to tailor specs and plans
  • Gatekeeping with HARD-GATE to prevent implementation until approval
  • Generation of design documents, implementation plans, and optional stories.yaml for autonomous execution
  • Supports Full, Lite, and Minimal modes for varied autonomy levels and project sizes

Quick Start

Announce PREVC planning and begin with gathering project context, running the 9-step brainstorming, and scaffolding the implementation plan.

Frequently Asked Questions about prevc-planning

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

FAQPage Schema
How do I turn a software idea into a validated implementation plan?

To turn a software idea into a validated implementation plan, use a structured brainstorming process that gathers context, runs Socratic design exploration, and scaffolds a written spec with test-first ordering before any code is written.

What is Socratic brainstorming for software design specs?

Socratic brainstorming for software design specs is a structured 9-step question-and-answer process that explores design decisions and enriches context, ensuring ideas are fully validated before formalizing them into implementation roadmaps.

How do I prevent premature coding during the planning phase?

To prevent premature coding during the planning phase, impose a hard gate that blocks implementation until a written design spec and a test-first implementation plan are formally approved.

Can I generate autonomous execution stories from a design spec?

Yes, you can generate autonomous execution stories from a design spec by creating a stories.yaml file, which translates the validated implementation plan into structured stories for autonomous execution.

Does PREVC planning support different project sizes and autonomy levels?

PREVC planning supports different project sizes and autonomy levels through Full, Lite, and Minimal modes, allowing you to tailor the context gathering and spec enrichment process to your specific project requirements.

What is the best way to write a test-first implementation plan?

The best way to write a test-first implementation plan is to coordinate context enrichment with formal scaffolding, ensuring the plan dictates test ordering and establishes guardrails before handing off to execution.