planning

Explore codebases and documentation to plan software feature implementation.

18|5|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/jnarowski/agentcmd --skill planning-jnarowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/jnarowski/agentcmd/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/jnarowski/agentcmd --skill planning-jnarowski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of software development by providing a structured approach to planning, researching, and clarifying feature requirements before any code is written.

Core Features & Use Cases

  • Codebase Exploration: Systematically investigate existing code patterns, architecture, and relevant files.
  • Context Gathering: Leverage internal documentation, project rules (CLAUDE.md), and external resources (via context7 MCP) for comprehensive understanding.
  • Clarification & Assessment: Ask targeted, one-at-a-time questions to resolve ambiguities and assess feature complexity.
  • Use Case: Before implementing a new user notification system, use this Skill to research existing notification patterns, understand the required data models, and clarify whether to use WebSockets or a different approach, ensuring a well-defined plan before spec generation.

Quick Start

Use the planning skill to research and plan the implementation of a new user authentication flow.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I research a codebase before implementing a new feature?

To research a codebase for feature implementation, systematically explore existing code patterns, architecture, and relevant files while gathering context from internal documentation to clarify requirements before generating specs.

What is the best way to assess feature complexity before writing code?

Assessing feature complexity involves clarifying implementation details through structured, one-at-a-time questioning to resolve ambiguities, ensuring a well-defined plan is prepared before any spec generation or coding begins.

How do I clarify ambiguities in software requirements during the planning phase?

Clarify ambiguities in software requirements by asking targeted questions one at a time, investigating existing code patterns, and gathering context from project rules and external documentation to resolve implementation uncertainties.

Can I use internal documentation and external resources for codebase exploration?

Codebase exploration can leverage internal documentation, project rules like CLAUDE.md, and external resources via context7 MCP to achieve comprehensive understanding of existing architecture and relevant files.

Do I need to clarify architecture patterns before planning a user authentication flow?

Clarifying architecture patterns before planning a user authentication flow is essential to research existing notification or authentication patterns, understand required data models, and evaluate approaches like WebSockets before spec generation.