vf-planning

Establish and maintain structured planning documentation for non-development labs.

9|Updated May 24, 2026
One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill vf-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vf-planning
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/planning-core
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill vf-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents planning drift and context loss by keeping a lab's current state, future direction, decisions, and work history in structured, reconstructible files.

Core Features & Use Cases

  • Adaptive Planning Scaffolding: Creates and maintains a minimal or rigorous planning foundation based on the lab's actual domain and workflow.
  • Compartment-Aware Organization: Supports multi-project labs with steering documents, indexed compartments, conditional plans, and deliverable or continuous work types.
  • Planning Enforcement and Memory Bridging: Checks state freshness, detects planning debt, injects focused planning context, guards against unrecorded deliverable changes, and connects planning records with durable memory.
  • Use Case: Give the Skill a content, sales, research, or operations lab and it can determine the appropriate planning profile, establish the relevant documentation structure, and keep the active state current without imposing a software-development workflow.

Quick Start

Ask the vf-planning skill to structure the documentation and establish tracking for this lab.

Frequently Asked Questions about vf-planning

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

FAQPage Schema
How do I prevent planning drift and context loss in a non-development project lab?

Preventing planning drift and context loss requires structured documentation that tracks a lab's current state, decisions, and work history. This Skill establishes a planning foundation that keeps active state current and reconstructible without imposing software-development workflows.

What is planning debt and how do I detect it in project management?

Planning debt occurs when project state and decisions go unrecorded. This Skill detects planning debt by checking state freshness, guarding against unrecorded deliverable changes, and connecting planning records with durable memory to ensure continuous context alignment.

How do I set up compartment-aware documentation for a multi-project lab?

Setting up compartment-aware documentation involves creating steering documents, indexed compartments, and conditional plans. This Skill organizes multi-project labs by supporting both deliverable and continuous work types within an adaptive planning topology.

Can I use a planning scaffold for content, sales, or research labs without external dependencies?

Yes, you can establish a planning scaffold for content, sales, or research labs without external dependencies. This Skill applies shell-based enforcement hooks to create domain-adapted documentation and tracking for non-development labs independently.

What is the best way to maintain state freshness across multiple lab workflows?

Maintaining state freshness requires automated checks and memory bridging. This Skill performs state freshness checks, injects focused planning context, and bridges planning records with durable memory to keep multi-project lab workflows synchronized.

Do I need a software development workflow to track lab deliverables and continuous work?

No, a software development workflow is not required to track lab deliverables. This Skill establishes a domain-adapted planning foundation that supports both deliverable and continuous work types for non-development labs like operations, design, or casework.