planning-blueprinting

Manage software project plans and specifications with status tracking in-repo.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/constructive-io/constructive-skills --skill planning-blueprinting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-blueprinting
Source: https://github.com/constructive-io/constructive-skills/tree/main/skills/planning-blueprinting
Command: npx skills add https://github.com/constructive-io/constructive-skills --skill planning-blueprinting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured system for creating, reviewing, and formalizing software plans and specifications directly within a codebase, ensuring clarity and alignment throughout the development lifecycle.

Core Features & Use Cases

  • Iterative Planning: Facilitates the creation of draft proposals and blueprints for new features or architectural changes.
  • Formal Specification: Enables the promotion of accepted plans into authoritative contracts that define behavior and requirements.
  • Status Tracking: Implements a two-axis system for tracking both the decision lifecycle (Draft, Accepted, Deprecated) and implementation progress (Not Implemented, In Progress, Implemented).
  • Use Case: When tasked with designing a new user authentication module, use this skill to create a detailed plan, track its review, and then formalize it as a specification that engineers and QA can use as a definitive guide.

Quick Start

Use the planning-blueprinting skill to create a new plan for the upcoming user profile feature.

Frequently Asked Questions about planning-blueprinting

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

FAQPage Schema
How do I document software specifications and manage project plans within a repository?

To document software specifications in a repository, establish a system using distinct plan and spec concepts to manage the lifecycle from proposal to authoritative contract, tracking both decision and implementation phases.

What is the best way to track the implementation status of software design proposals?

Track implementation status of software design proposals using a two-axis system that monitors both the decision lifecycle (Draft, Accepted, Deprecated) and implementation progress (Not Implemented, In Progress, Implemented).

How do I formalize a draft architectural blueprint into an authoritative contract?

Formalize a draft architectural blueprint into an authoritative contract by promoting accepted plans, ensuring clarity and alignment throughout the development lifecycle for engineers and QA.

Can I use in-repo planning for iterative feature design without external documentation tools?

Yes, you can use in-repo planning for iterative feature design by creating draft proposals and blueprints for new features or architectural changes directly within the codebase.

When do I need a formal specification system for software project planning?

You need a formal specification system for software project planning when creating, reviewing, and formalizing software plans to ensure clarity and alignment throughout the development lifecycle.

Does the planning-blueprinting skill support architectural planning for any type of project?

Yes, the planning-blueprinting skill supports architectural planning and documentation within any project by establishing an in-repo system for specification using distinct plan and spec concepts.