skills.rest
macollins27
macollins27COMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan

Produces design.md, plan.md and codebase-context.md from a spec and codebase context.

Updated Aug 23, 2026
Search Tags:#planning#architecture#spec#guardrails#codebase-context#design-doc
One-click install
npx skills add https://github.com/macollins27/guardrails-plugin --skill plan-macollins27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/macollins27/guardrails-plugin/tree/main/skills/plan
Command: npx skills add https://github.com/macollins27/guardrails-plugin --skill plan-macollins27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning architecture from a completed spec to produce design.md, plan.md, and codebase-context.md, reducing manual drafting and ensuring alignment with truth documents.

Core Features & Use Cases

  • Orchestrates end-to-end architecture planning by loading constraints, extracting the spec, auditing the codebase, generating design artifacts, and validating with a reviewer.
  • Produces design.md, plan.md, and codebase-context.md that are ready for implementation by agent teams.
  • Supports gated review and gate checks to ensure build and tests pass before handoff.

Quick Start

Follow /guardrails:plan workflow to generate architecture artifacts from a completed spec.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate architecture design documents from a feature spec?▼

You generate architecture design documents by consuming a completed feature spec and current codebase context to produce design.md, plan.md, and codebase-context.md. This planning process reduces manual drafting and enforces frontmatter constraints.

What is the best way to plan software architecture before handing off to agent teams?▼

Planning software architecture for agent teams requires a gated workflow that audits the codebase, generates design artifacts, and validates with a reviewer. This ensures build and tests pass before implementation handoff.

Do I need a completed spec before starting architecture planning?▼

Yes, architecture planning requires a completed feature spec as input. The workflow extracts the spec, audits the codebase, and traces every decision to defined truth documents and user answers to produce valid artifacts.

Can I enforce frontmatter constraints and naming conventions in generated design docs?▼

Yes, the architecture planning workflow enforces frontmatter constraints and supports required artifact naming and structure. It validates design.md, plan.md, and codebase-context.md through reviewer gating checks before handoff.

How does codebase context auditing work during architecture design?▼

Codebase context auditing works by analyzing the existing codebase alongside a completed spec to extract relevant constraints. This produces codebase-context.md, ensuring architecture decisions trace to defined truth documents.

Related Skills

Explore More Software Engineering Skills→
withpiperwithpiper
6

light-spec

Generate a structured light spec from a Linear issue for VBW planning ingestion.

Official
Intermediate
Ankurjain1121Ankurjain1121

spec-driven-development

Generate a specs directory with design, API contracts, modules, implementation order, and constraints.

Community
Basic
AAbdulghanyAAbdulghany

code-review

Automate pull request reviews with role-based gating and human sign-off.

Community
Advanced
pretodevpretodev
1

creating-feature-spec

Generate structured feature specification documents from feature definitions.

Community
Intermediate