planning

Automate lifecycle management of planning documents with consistent numbering and frontmatter.

3|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/mjrskiles/vibe-hacker --skill planning-mjrskiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/mjrskiles/vibe-hacker/tree/main/plugins/planning/skills/planning
Command: npx skills add https://github.com/mjrskiles/vibe-hacker --skill planning-mjrskiles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires frontmatter, and includes scripts (resource) components.

What problem does it solve?

This Skill enforces consistent planning documentation workflows, ensuring proper numbering, frontmatter metadata, and lifecycle management across ADRs, FDPs, APs, and reports.

Core Features & Use Cases

  • Auto-numbering & routing: Creates new documents with correct IDs and directory structure.
  • Lifecycle management: Enforces status transitions, archiving, and addenda without editing locked docs.
  • Cross-document relationships: Supports linking related documents and supersedes relationships.
  • Protected paths & templates: Applies structure and templates to keep docs consistent.

Quick Start

python3 ${CLAUDE_PLUGIN_ROOT}/skills/planning/scripts/new.py adr "New Architecture Decision"

Frequently Asked Questions about planning

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

FAQPage Schema
How do I automate numbering and lifecycle management for architecture decision records?

Architecture decision records (ADRs) require consistent numbering and status tracking across creation, archiving, and updates. This Skill automates ID generation, enforces proper directory routing, manages lifecycle transitions, and maintains frontmatter structure so you maintain a searchable, organized record without manual intervention.

Can I enforce consistent metadata and relationships across planning documents like ADRs and FDPs?

Yes. This Skill applies frontmatter templates, auto-numbering, and cross-document linking to ADRs, FDPs, action plans, and reports. It enforces status transitions, supersedes relationships, and addenda management, keeping all planning documents structurally consistent without editing locked files.

What's the best way to organize and archive planning documents while preserving their relationships?

The Skill automates archive handling and inter-document relationships through configuration-driven lifecycle management. It moves documents to archive directories, maintains links between related records, and tracks supersedes relationships, so your planning history remains intact and queryable.

How do I set up auto-numbering templates for new planning documents?

Configure vibe-hacker.json to define directory structure and numbering rules for each document type (ADR, FDP, AP, Report). The Skill reads this configuration and applies it when you create new documents, generating correct IDs and frontmatter automatically via the provided Python scripts.

Can I use this with existing documentation workflows without rewriting my docs?

The Skill applies structure to new documents you create going forward. It protects existing content through frontmatter parsing and status management, so you can integrate it incrementally into your workflow without disrupting your current planning documentation.