plan

Included with Lifetime

$97 forever

Generate an implementation plan from a specification. Phase 2 of Spec Kit workflow.

General

What this skill does


# Generate Implementation Plan

Generate an implementation design document from a canonical specification.

## Workflow

1. **Load Specification**
   - Read the specification file from provided path
   - If no path provided, search `.specs/` for recent specifications
   - Parse requirements and acceptance criteria

2. **Analyze Codebase**
   - Explore existing codebase for:
     - Existing patterns and conventions
     - Related components and modules
     - Integration points
     - Technology stack

3. **Generate Design**
   - Create implementation approach
   - Identify components to create/modify
   - Define data models (if applicable)
   - Design API contracts (if applicable)
   - Document alternatives considered
   - Map design elements to requirements

4. **Validate Coverage**
   - Verify design addresses all requirements
   - Check alignment with codebase conventions
   - Identify risks and mitigation strategies

5. **Save Design**
   - Save to `.specs/{feature-name}/design.md`
   - Update specification with design reference
   - Report design summary

## Arguments

- `$ARGUMENTS` - Path to specification file

## Examples

```bash
# From specification file
/spec-driven-development:plan .specs/user-auth/spec.md

# Auto-detect recent specification
/spec-driven-development:plan
```

## Design Document Structure

```markdown
# Design: {Feature Name}

## Overview
[High-level implementation approach]

## Components

### {Component 1}
- **Responsibility:** [What it does]
- **Location:** [File path]
- **Interfaces:** [How it connects]

## Data Model
[Entity definitions if applicable]

## API Design
[Endpoint specifications if applicable]

## Alternatives Considered
[Other approaches and why rejected]

## Requirements Coverage
| Requirement | Covered By |
| --- | --- |
| FR-1 | Component A |
| FR-2 | Component B |
```

## Related Commands

- `/spec-driven-development:specify` - Generate specification (Phase 1)
- `/spec-driven-development:tasks` - Generate task breakdown (Phase 3)
- `/spec-driven-development:implement` - Guide implementation (Phase 4)

Files: 1

Size: 2.3 KB

Complexity: 9/100

Category: General

Source: https://github.com/melodic-software/claude-code-plugins/tree/main/plugins/spec-driven-development/skills/plan

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts