plan

Translate user prompts into build-ready specifications with goals and dependency graphs.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Nerfherder16/BrickLayer --skill plan-nerfherder16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Nerfherder16/BrickLayer/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/Nerfherder16/BrickLayer --skill plan-nerfherder16

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning vague planning questions into a concrete, build-ready specification for Autopilot workflows by guiding exploration of the codebase, capturing goals, constraints, and dependencies.

Core Features & Use Cases

  • Spec drafting: Converts prompts into a detailed .autopilot/spec.md with goals, tasks, tests, and constraints.
  • Dependency planning: Generates a dependency graph and phase_end markers to structure large builds.
  • Codebase exploration: Reads relevant files and recalls prior context to inform the spec.

Quick Start

Plan a planning session by prompting with a concrete objective and let the agent generate a complete build-ready spec.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a vague prompt into a build-ready spec for a codebase?▼

A build-ready spec is generated by translating a concrete objective through a guided planning session. It captures goals, task lists, files to modify, tests, and clear out-of-scope items to structure your codebase builds effectively.

What is SPARC mode annotation and how does it structure autopilot workflows?▼

SPARC mode annotations are structural markers applied during spec planning to guide autopilot workflows. They organize large builds by defining dependency graphs and phase_end markers, ensuring structured and phased development.

Can I generate a dependency graph for large build processes using a spec?▼

Yes, generating a dependency graph for large build processes is achieved by drafting a detailed specification. The spec maps dependencies and inserts phase_end markers to sequence tasks, structuring the complete build process.

What should be included in an autopilot spec.md file?▼

An autopilot spec.md file must include project goals, success criteria, task lists, files to modify, tests, and design constraints. It also defines clear out-of-scope items and dependency graphs to prepare for structured builds.

Does spec-writing work for codebases of varying sizes?▼

Yes, this spec-writing approach applies to projects of varying sizes. It guides codebase exploration and recalls prior context to inform the specification, ensuring the build plan scales appropriately with your project requirements.