plan

Name: plan
Availability: InStock
Author: NooBat

Generate phased, design-driven implementation plans from codebase scans.

Updated Mar 23, 2026

Search Tags:#workflow #planning #architecture #codebase #plan #software-engineering

Ready to run

npx skills add https://github.com/NooBat/claude --skill plan-noobat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/NooBat/claude/tree/main/skills/plan
Command: npx skills add https://github.com/NooBat/claude --skill plan-noobat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables building implementation plans that are grounded in the existing codebase and patterns, preventing reinvention and reducing risk.

Core Features & Use Cases

Codebase-aware planning: generate technical designs and phased tasks based on real project structure, utilities, and patterns.
One-story-per-plan: focus planning on a single user story with clear scope, constraints, and success criteria.
Ad-hoc spec handling: ingest a spec or gather requirements when none exists, to drive a focused plan.

Quick Start

Instruct the system to create a codebase-aware implementation plan for the current feature using the repository.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I create a codebase-aware implementation plan for a new user story?▼

Create a codebase-aware implementation plan by scanning existing project structures and patterns, then producing a phased, design-driven plan with concrete interfaces, exact file paths, and testing guidance.

What is the best way to plan software architecture without reinventing existing code patterns?▼

The best way to plan software architecture without reinventing patterns is to reconcile specifications against a codebase scan, ensuring the implementation plan grounds new designs in existing utilities and structures.

Can I generate a phased technical design plan if I only have ad-hoc requirements instead of a spec?▼

Yes, you can generate a phased technical design plan from ad-hoc requirements by ingesting the gathered requirements to drive a focused plan that specifies data models and exact file paths.

How does codebase scanning improve software engineering workflow planning?▼

Codebase scanning improves software engineering workflow planning by reconciling existing project patterns and structures with the target spec, reducing implementation risk and preventing pattern reinvention.

What limitations exist when planning a feature that spans multiple user stories at once?▼

A key limitation is that this planning approach focuses strictly on one user story per plan, requiring you to split larger features into individual stories to maintain clear scope and success criteria.