feature-implement

Included with Lifetime

$97 forever

Execute a feature implementation plan from a clean context. Use when starting implementation after planning, or when resuming work on an in-progress feature. Reads plan.md and executes implementation steps.

General

What this skill does

# Implement Feature

You are executing the **IMPLEMENT FEATURE** workflow — picking up a plan and executing it with a clean context.

## Target Feature

$ARGUMENTS

## Step 1: Load the Plan

1. If a feature ID was provided above, read `docs/features/<id>/plan.md`
2. If no ID was provided, read `docs/features/DASHBOARD.md` and show the **In Progress** features. Ask the user which one to implement.
3. Also read `docs/features/<id>/idea.md` for the original problem statement and context.

If the plan doesn't exist, suggest running `/feature-workflow:feature-plan` first.

### State Guard

Read `idea.md` `state:` field. If state is `paused`, `replaced`, or `abandoned`, stop and tell the user the same way `/feature-plan` does. Do NOT continue with implementation steps.

Tracking-progress edits to plan.md are allowed for paused features — that's a deliberate exception so completed steps can be checked off when work resumes. The block is on starting *new* implementation work.

## Step 2: Set Context

Set the statusline so the user can see which feature is active:

```bash
python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/statusline.py set <feature-id>
```

## Step 3: Review and Confirm

Present a brief summary:
- Feature name and ID
- Number of implementation steps
- Which steps are already checked off (if resuming)
- First uncompleted step

Ask the user: **"Ready to start? Any changes to the plan before we begin?"**

## Step 4: Execute Implementation Steps

Work through the implementation steps from plan.md sequentially:

1. For each step:
- State what you're about to do
- Implement it
- Run relevant tests
- Mark the step complete in plan.md using `/feature-workflow:tracking-progress`

2. After completing each step, briefly summarize what was done and what's next.

3. If you hit a blocker:
- Explain the issue clearly
- Suggest alternatives
- Ask the user how to proceed
- Consider if this is scope creep — use `/feature-workflow:guarding-scope` if needed

## Step 5: Completion

When all steps are done:

1. Run the full test suite
2. Summarize what was implemented
3. Check if the plan was reviewed: look for a PR on `feature/<id>` with plan review comments. If none exists, warn:
**"Note: The plan hasn't been through external review yet. Consider running `/feature-review-plan <id>` before submitting the implementation."**
4. Suggest the next step: **`/feature-review-impl <id>`** — this pushes the implementation to the feature branch and updates the draft PR for external code review by Gemini/Codex.

The full workflow is: `/feature-capture` → `/feature-plan` → `/feature-review-plan` → `/feature-implement` → **`/feature-review-impl`** → `/feature-ship`

Do not suggest `/feature-ship` directly — that's the final merge step, run after reviews are satisfactory.

## Guidelines

- **Stay focused on the plan** — don't add unplanned features
- **Test as you go** — don't defer all testing to the end
- **Update progress** — keep plan.md checkboxes current
- **Ask when uncertain** — the plan may not cover every edge case

Files: 1

Size: 3.3 KB

Complexity: 12/100

Category: General

Source: https://github.com/schuettc/claude-code-plugins/tree/main/feature-workflow/skills/feature-implement

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