implementing-stories

Included with Lifetime

$97 forever

Implement using TDD Red-Green cycle. Focus on Red-Green only; refactoring is separate step.

General

What this skill does


# Implementing Stories (Red-Green)

Implement using TDD Red-Green cycle. Refactoring happens separately with fresh context.

## Context

Find story log, understand codebase, identify what to implement.

## Principles

- Small steps: one behavior at a time
- Test-driven: write test first
- Red-Green focus: get tests passing, skip cleanup

## TDD Cycle

### Red: Write Failing Test

- [ ] Write test defining behavior
- [ ] Scaffold symbols (avoid "not found")
- [ ] Confirm fails for right reason

**Key**: Fails because feature missing, not syntax error.

### Green: Make It Pass

- [ ] Implement minimum to pass
- [ ] No extras or cleanup
- [ ] Confirm passes

Don't worry about quality/duplication. Refactoring is next phase.

## Map Criteria

For each criterion:
1. Identify behavior
2. Write test (Given-When-Then)
3. Implement minimum
4. Next criterion (skip refactoring)

## Update Story Log (REQUIRED)

**CRITICAL**: Must update before finishing.

```markdown
### Implementation (Red-Green)

**Status: Complete - Ready for Refactor**

**Implemented:**
- [Criterion]: [Approach]

**Decisions:**
- [Decision]: [Why]

**Tests:**
- [Test file]: [What tests]
- Status: All passing (X)

**Technical debt:**
- [Item]: Duplication needing refactor
- [Item]: Naming improvements

**Next:** Refactor
```

Steps:
1. Find story log (docs/stories/**/*.story.md)
2. Update "Completed Work Summary"
3. Save and verify

## When to Stop

- All criteria have passing tests
- All tests pass
- No syntax/type errors
- **Story log updated**

**Only after story log updated**, pass to Refactor.

## Pitfalls

- Skipping tests
- Big steps
- Premature cleanup (resist refactoring)
- Ignoring error handling
- Over-implementation

Files: 1

Size: 1.8 KB

Complexity: 4/100

Category: General

Source: https://github.com/kecbigmt/cc-plugins/tree/main/plugins/story-driven/skills/implementing-stories

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