spec-from-stories

Included with Lifetime

$97 forever

Use to derive a spec from user stories / Jira tickets / Linear issues. Aggregates the stories, finds the underlying capability, produces a spec with testable AC. Inverse of "spec → tickets".

General

What this skill does


# spec-from-stories

User stories → coherent spec. The opposite of breaking a spec into tickets — given the tickets, recover the spec.

## Method

1. **Gather stories.** User pastes them, points to a ticket query, or supplies a list. Ideal input is 3-15 related stories.
2. **Cluster.** Group by capability. A spec covers ≥ 1 cluster; multiple specs may emerge.
3. **Per cluster:**
   - Distil the underlying capability ("the user wants to do X")
   - Map each story to a slice of the capability
   - Find gaps — capability requires X but no story addresses it
   - Find overlaps — multiple stories asking for the same thing in different words
4. **Synthesise spec.** Standard shape: overview, actors, behaviour, acceptance criteria, edge cases, non-goals.
5. **Backlink.** Each AC cites the originating story IDs. Easy to pivot back.

## Output shape

```
Stories input:    N (e.g. STORY-1 to STORY-15)

Clusters:
  Cluster A — checkout (8 stories)
  Cluster B — search   (4 stories)
  Cluster C — outliers (3 stories — possibly noise)

---

# Spec: Checkout

## Overview
<one paragraph distilled capability>

## Actors
- Anonymous shopper
- Signed-in shopper
- (admin not in scope)

## Behaviour
- ...

## Acceptance Criteria
- AC1 [STORY-1, STORY-7]    <criterion>
- AC2 [STORY-3]             <criterion>
- AC3 [STORY-9, STORY-11]   <criterion>

## Edge Cases
- ...

## Non-goals
- Subscriptions (separate spec)

## Open questions (gaps in the stories)
- Q1: STORY-5 implies guest checkout but no story specifies idempotency
- Q2: <missing capability>

## Story coverage
  Mapped:        8 of 8 cluster A stories
  Outlier:       3 stories don't fit (suggest separate spec or reject)
```

## Rules

- **Backlink every AC** to source story IDs.
- **Surface outliers.** Stories that don't cluster get their own callout — don't force-fit.
- **Surface gaps.** Capability requires X but no story addresses it → open question.
- **Don't invent.** If 3 stories say "checkout should be fast", don't infer a SLA — flag as ambiguous.

## Anti-patterns

- Treating all stories as equally weighted
- Hiding outliers in the synthesis
- Inventing requirements not present in any story
- Long preambles before the spec — get to the structure

## When NOT to use

- Single ticket (no cluster to derive)
- Greenfield (no stories yet) — `/dream` or PRD-from-scratch
- After spec exists — `/improve-spec` instead

## Subagent dispatch

- `Plan` for cluster + spec synthesis
- `general-purpose` for the backlink mapping
- Memory MCP for prior specs on adjacent capabilities

## Value over native CC

CC will summarise stories. CC won't naturally cluster by capability, surface outliers, backlink ACs to source stories, or flag gaps. The structure IS the value.

Files: 1

Size: 2.9 KB

Complexity: 7/100

Category: General

Source: https://github.com/ialameh/sift-coder/tree/main/skills/spec/spec-from-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