feature

Included with Lifetime

$97 forever

Generate a comprehensive feature implementation plan with user story, phases, and testing strategy. Use when planning new functionality before implementation.

General

What this skill does


# Feature Planning

Create a new plan in `specs/*.md` to implement the Feature using the exact specified markdown Plan Format. Follow the Instructions to create the plan, use the Relevant Files to understand existing patterns.

## Instructions

- You are writing a plan to implement a feature, NOT implementing it yet
- Use your reasoning model: THINK HARD about the architecture and implementation approach
- Read the codebase to understand existing patterns, styles, and conventions
- Focus on the files in the Relevant Files section when designing the implementation
- Fill in EVERY section of the Plan Format - especially Testing Strategy
- Break the Implementation Plan into Foundation, Core, and Integration phases
- Include validation commands that prove the feature works end-to-end
- Consider edge cases and error scenarios in your planning

## Relevant Files

Focus on the following files to understand the codebase:

- README.md (project structure and conventions)
- CLAUDE.md (agent instructions if present)
- src/**or app/** (source code patterns to follow)
- tests/** (testing patterns and conventions)
- package.json or pyproject.toml (dependencies)
- docs/** (existing documentation style)

## Plan Format

Write the plan to `specs/feature-<descriptive-name>.md` using this exact format:

```markdown
# Feature: <descriptive-name>

## Feature Description
<Clear explanation of the feature and its value to users>

## User Story
As a <role>, I want <capability> so that <benefit>.

## Problem Statement
<What user need or pain point does this feature address>

## Solution Statement
<High-level description of how this feature solves the problem>

## Relevant Files
<Files to create or modify, organized by type>

### New Files
- <path/to/new/file.ts> (purpose)

### Modified Files
- <path/to/existing/file.ts> (what changes)

## Implementation Plan

### Foundation Phase
<Setup, dependencies, configuration, scaffolding>

### Core Phase
<Main feature implementation - the primary logic>

### Integration Phase
<Connecting components, wiring up, final touches>

## Step by Step Tasks
1. <First task with specific file references>
2. <Continue with numbered, specific tasks>

## Testing Strategy

### Unit Tests
<Component and function-level tests to write>

### Integration Tests
<Cross-component and API tests to write>

### Edge Cases
<Boundary conditions and error scenarios to test>

## Acceptance Criteria
- [ ] <Specific criterion that can be verified>
- [ ] <Another criterion>
- [ ] <Continue criteria>

## Validation Commands
<Commands that prove the feature works>
- Run `<test command>` to verify unit tests pass
- Run `<test command>` to verify integration tests pass
- Run `<build command>` to verify build succeeds
- Manual verification: <steps to manually test>

## Notes
<Future enhancements, related features, technical debt, dependencies>
```

## Feature

$ARGUMENTS

Files: 1

Size: 3.1 KB

Complexity: 11/100

Category: General

Source: https://github.com/melodic-software/claude-code-plugins/tree/main/plugins/tac/skills/feature

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