AgentSkillsCN

vibeflow-planning

为VibeFlow文档优先型工作流的A-D阶段创建规划文档

SKILL.md
--- frontmatter
name: vibeflow-planning
description: Create planning documents for Stages A-D of the VibeFlow docs-first workflow
metadata:
  triggers:
    - create PRD
    - write PRD
    - product requirements
    - discovery
    - analyze codebase
    - Stage B
    - tech spec
    - specification
    - Stage C
    - ADR
    - decision record
    - Stage D
    - plan feature
    - planning phase

vibeflow-planning

Create planning documents for Stages A-D of the VibeFlow docs-first workflow.

Purpose

This skill helps create and validate planning documents:

  • •PRD (Stage A) — Product requirements
  • •Discovery (Stage B) — Codebase analysis
  • •Tech Specs (Stage C) — System specifications
  • •ADRs (Stage D) — Architectural decisions

Triggers

Use this skill when:

  • •User asks to "create PRD", "write PRD", "product requirements"
  • •User asks for "discovery", "analyze codebase", "Stage B"
  • •User asks for "tech spec", "specification", "Stage C"
  • •User asks for "ADR", "decision record", "Stage D"
  • •User says "plan feature", "planning phase"

Usage

Create PRD

code
/vibeflow-planning prd

Creates or updates docs/prds/prd.md with required sections.

Create Discovery Document

code
/vibeflow-planning discovery <ID>

Creates docs/discovery/disco-<ID>.md with all 5 phases.

Example:

code
/vibeflow-planning discovery 030

Create/Update Tech Spec

code
/vibeflow-planning spec <spec-name>

Creates or updates docs/specs/spec-<name>.md.

Example:

code
/vibeflow-planning spec api
/vibeflow-planning spec llm

Create ADR

code
/vibeflow-planning adr <ID> <slug>

Creates docs/adrs/adr-<ID>-<slug>.md.

Example:

code
/vibeflow-planning adr 001 backend-framework

Validate Planning

code
/vibeflow-planning validate

Runs Checkpoint #1 validation on all planning documents.

Document Requirements

PRD (docs/prds/prd.md)

Required sections:

  • •Header (version, file, owners, last_updated)
  • •Summary (3-5 lines)
  • •Problem & Context
  • •Users & Use Cases
  • •Scope (MoSCoW format)
  • •Success Metrics (baseline → target)
  • •Non-Goals
  • •Requirements (functional + non-functional)
  • •Dependencies
  • •Risks & Mitigations
  • •Analytics & Telemetry

Discovery (docs/discovery/disco-<ID>.md)

Required phases:

  • •Phase 0: Spec Discovery (analyze existing specs)
  • •Phase 1: Spec-Code Validation (verify accuracy)
  • •Phase 2: Test Impact Analysis (test update checklist)
  • •Phase 3: Dependency & Side Effect Mapping
  • •Phase 4: Reusable Component Discovery
  • •Risk Assessment & Go/No-Go Recommendation

Tech Spec (docs/specs/spec-<name>.md)

Required sections:

  • •Header (version, status, PRD link, contract versions)
  • •Overview & Goals
  • •Architecture (topology diagram + component inventory)
  • •Interfaces & Data Contracts
  • •Data & Storage
  • •Reliability & SLIs/SLOs
  • •Security & Privacy
  • •Evaluation Plan

ADR (docs/adrs/adr-<ID>-<slug>.md)

Required sections:

  • •Title with decision summary
  • •Header (File, Status)
  • •Context
  • •Decision
  • •Consequences (+/-)
  • •Alternatives
  • •Rollback Plan
  • •Links (PRD/SPEC/FEATURE references)

Validation Scripts

The following scripts validate planning documents:

  • •scripts/validate_prd.py — Validate PRD structure and content
  • •scripts/validate_discovery.py — Validate discovery document
  • •scripts/validate_techspec.py — Validate tech spec
  • •scripts/validate_adr.py — Validate ADR

Templates

See references/ for document templates:

  • •prd-template.md — PRD template
  • •discovery-guide.md — Discovery phases guide
  • •techspec-template.md — Tech spec template
  • •adr-template.md — ADR template

Checkpoint #1

After completing Stages A-D, validate with:

code
/vibeflow-validate checkpoint 1

This validates:

  • •PRD exists with all sections
  • •Discovery completed (Medium/Large)
  • •Tech Specs have architecture diagram and inventory
  • •ADRs exist for non-trivial decisions