planning

Manage subsystem roadmap lifecycles and enforce dependency resolution in CodeGG.

Updated May 6, 2026
One-click install
npx skills add https://github.com/dbowm91/codegg --skill planning-dbowm91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/dbowm91/codegg/tree/main/.opencode/skills/planning
Command: npx skills add https://github.com/dbowm91/codegg --skill planning-dbowm91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured governance framework for managing the lifecycle of CodeGG subsystems, ensuring that architectural decisions, implementation plans, and closure evidence are tracked consistently and transparently.

Core Features & Use Cases

  • Registry Management: Maintains a central control surface for tracking the status of all active subsystem roadmaps and implementation milestones.
  • Evidence-Based Closure: Enforces a rigorous gatekeeping process where milestones are only marked closed upon verification of production evidence and invariant checks.
  • Dependency Tracking: Automatically manages the unblocking of downstream work by auditing dependency graphs whenever a milestone is successfully closed.

Quick Start

Use the planning skill to register a new implementation plan for the session-projections subsystem as active in the registry.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I manage subsystem roadmaps and track milestones across multiple states?

Subsystem roadmaps are managed by tracking work items through defined states like proposed, active, and closed, ensuring traceability and long-term stability within a structured governance framework.

How do I enforce dependency resolution when closing implementation milestones?

Dependency resolution during milestone closure is enforced by auditing dependency graphs and automatically unblocking downstream work whenever an upstream milestone is successfully verified and closed.

What is the best way to require production evidence before marking a roadmap milestone as closed?

Evidence-based closure requires a rigorous gatekeeping process where milestones are only marked closed upon verification of production evidence and invariant checks.

Can I use a central registry to track the status of all active subsystem implementation plans?

Yes, registry management provides a central control surface for tracking the status of all active subsystem roadmaps and implementation milestones.

Does architectural consistency require a specific document hierarchy for lifecycle management?

Yes, architectural consistency requires adherence to an established document hierarchy and status vocabulary to ensure traceability and long-term stability throughout the lifecycle.

When should I not use a structured governance framework for subsystem planning?

Structured governance frameworks for subsystem planning should be avoided when a project lacks defined architectural invariants or requires rapid prototyping without strict milestone gatekeeping.