start-new-feature

Included with Lifetime

$97 forever

Starts a new feature in a new branch. Use when the user asks to create a new feature, build something new, or says "new feature", "start feature", or "let's build". Creates a feature branch, enters plan mode, interviews the user, validates with experts, and saves the spec.

General

What this skill does

# Start New Feature

Follow every step below in order. Do not skip any step.

## Step 1: Create the feature branch

- Derive `<feature-name>` from the user's request as a concise, hyphenated slug.
- Create and checkout the branch using the naming convention `feature/<feature-name>`.

```bash
git checkout -b feature/<feature-name>
```

## Step 2: Enter plan mode

- Use the `EnterPlanMode` tool to switch into plan mode.
- Begin drafting the implementation plan inside the plan file.

### Plan structure

Organize the plan in phases. Each phase must include:

- **Goal** — what the phase achieves.
- **Deliverables** — concrete outputs (files, migrations, tests, etc.).
- **Steps** — ordered implementation steps within the phase.

## Step 3: Interview the user

- Invoke the `interview` skill (`/interview`) to conduct an in-depth technical interview.
- Use the interview to clarify requirements, edge cases, UI/UX decisions, and technical tradeoffs.
- Incorporate all answers and decisions back into the plan.

## Step 4: Validate with expert agents

Once a first version of the plan exists, validate it by launching **all four** agents in parallel using the `Task` tool:

1. **Laravel Architect** (`subagent_type: "laravel"`) — review architecture, patterns, and Laravel conventions.
2. **Pest TDD Expert** (`subagent_type: "laravel:pest-tdd-expert"`) — review testing strategy, coverage, and TDD approach.
3. **Laravel Security Reviewer** (`subagent_type: "laravel:laravel-security-reviewer"`) — review for security vulnerabilities and OWASP concerns.
4. **Pest Browser Testing** (`subagent_type: "laravel:pest-browser-testing"`) — review browser/E2E testing strategy, UI interaction coverage, and accessibility checks.

Provide each agent with the full plan text and ask for feedback.

After collecting feedback from all three agents:

- Incorporate valid suggestions into the plan.
- If any agent raises a blocker, resolve it and re-validate that specific concern.

## Step 5: Finalize and exit plan mode

- Ensure the plan is complete with all phases, goals, deliverables, and steps.
- Use `ExitPlanMode` to present the plan to the user for approval.

## Step 6: Save the spec

After the user approves the plan:

- Create the `specs/` directory if it does not exist.
- Write the finalized plan to `specs/<feature-name>.md`.

Files: 1

Size: 2.6 KB

Complexity: 7/100

Category: General

Source: https://github.com/guetteman/claude-code/tree/main/plugins/laravel/skills/start-new-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