planning-guidance

Develop TDD-first implementation plans with functional-core/imperative-shell architecture.

3|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/driver-ai/driver-sdlc-plugin --skill planning-guidance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-guidance
Source: https://github.com/driver-ai/driver-sdlc-plugin/tree/main/skills/planning-guidance
Command: npx skills add https://github.com/driver-ai/driver-sdlc-plugin --skill planning-guidance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps software teams to streamline the planning phase of development by guiding them through the process of creating a robust, TDD-first implementation plan with functional-core/imperative-shell architecture.

Core Features & Use Cases

  • Architectural Guidance: Ensures the implementation plan follows a functional-core/imperative-shell architecture.
  • TDD-First Approach: Provides a methodology for writing tests before coding, ensuring high test coverage and quality.
  • Codebase Context: Gathers broad codebase context to inform the plan's architecture and testing strategy.
  • Task Breakdown: Delivers a detailed breakdown of tasks, enabling clear and manageable work units.
  • Use Case: A software developer uses this Skill to plan the implementation of a new feature, ensuring that the plan includes architectural decisions, a test strategy, and a task breakdown.

Quick Start

To create a plan for a new feature, use the planning-guidance skill and follow the steps outlined in the documentation.

Frequently Asked Questions about planning-guidance

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

FAQPage Schema
How do I create a TDD-first implementation plan for a new software feature?

Creating a TDD-first implementation plan involves analyzing broad codebase context to establish a functional-core/imperative-shell architecture, which then drives a detailed task breakdown for manageable development units.

What is functional-core/imperative-shell architecture in software development?

Functional-core/imperative-shell architecture separates pure business logic from side-effect handling, allowing a TDD-first approach to maximize test coverage and ensure robust software development.

How do I break down software development tasks for test-driven development?

Breaking down software tasks for TDD requires analyzing codebase context and architectural decisions to deliver clear, manageable work units that align testing strategy with development execution.

Do I need to analyze my codebase before generating an architectural plan?

Yes, analyzing the codebase is required because gathering broad codebase context directly informs the functional-core/imperative-shell architecture and the overall testing strategy for the implementation plan.

What's the best way to streamline software planning with architectural guidance?

Streamlining software planning is best achieved by integrating architectural guidance with a TDD-first approach, utilizing broad codebase context to produce a detailed task breakdown for efficient development.

Why does my software implementation plan lack a clear testing strategy?

Your implementation plan lacks a testing strategy because it fails to adopt a TDD-first approach, which requires gathering broad codebase context to inform both the architecture and the testing strategy.