pm-requirement

Included with Lifetime

$97 forever

Derive atomic, testable requirements from features. Each requirement is a single pass/fail statement. Every requirement must belong to a feature.

General

What this skill does


# PM Requirement — Bite-Sized Derivations

Derive specific, atomic requirements from features. Each requirement is a single testable statement — small enough for a clear pass/fail.

## Invocation

```
/pm-requirement myriplay crawl <feature-uuid>
/pm-requirement myriplay add <feature-uuid>
/pm-requirement myriplay list
/pm-requirement myriplay list feature=<uuid>
/pm-requirement myriplay show <uuid>
/pm-requirement myriplay edit <uuid>
```

## Database

**Path:** `.claude/db/marketing.sqlite` | `PRAGMA foreign_keys=ON;`

Uses `requirements` and `requirement_versions` tables.

## What is a Requirement?

A single, testable statement about system behavior. Smaller than a feature. Multiple requirements sum up to a feature being "done."

Examples:
- "System renders Host Cluster containers with CP and worker node counts"
- "System switches to compact layout when cluster count exceeds 50"
- "System supports rendering for each CLUSTER_TYPES" (uses iterator)

## Crawl Mode

1. Load parent feature by UUID — read its short_desc, detailed_desc, tags
2. Read relevant source material if available
3. Derive requirements — each one: title (imperative statement), description, acceptance_criteria
4. When a requirement applies across a set, reference iterators by name
5. INSERT each into `requirements` with `base_version` = parent feature's current `version`, `human_approved = 0`
6. INSERT version 1 into `requirement_versions`
7. Show summary with UUIDs

## Interact Mode (h/ai iterate)

1. Show parent feature for context
2. Ask: "What must be true for this feature to be complete?"
3. Human gives rough criteria — AI structures into formal requirements
4. Iterate each: title, description, acceptance_criteria
5. Accept: y/yes/ok/good
6. INSERT with `human_approved = 1`, `base_version` = parent feature's `version`
7. Show UUID: `Created requirement: <uuid> "title"`

## Edit

1. Show current requirement with parent feature context
2. Ask what to change
3. Run h/ai iterate on changed fields
4. Auto-increment `version` on `requirements`
5. Set `base_version` = current parent feature `version` (clears staleness)
6. INSERT new snapshot into `requirement_versions`

## Queries

```sql
-- List requirements for a feature
SELECT r.id, r.title, r.version, r.base_version, r.status, r.human_approved
FROM requirements r WHERE r.feature_id = :feature_uuid
ORDER BY r.title;

-- Requirements without tests
SELECT r.id, r.title FROM requirements r
LEFT JOIN product_feature_tests t ON t.requirement_id = r.id
WHERE r.feature_id = :feature_uuid AND t.id IS NULL;
```

## Rules

1. Every requirement belongs to exactly one feature.
2. `base_version` = parent feature's `version` at creation/confirmation.
3. Every edit auto-increments version and snapshots.
4. Reference iterators by name, never expand inline.
5. Always show UUID after create/edit.
6. Every requirement MUST eventually have a test (flag missing via `/pm-status`).

Files: 1

Size: 3.1 KB

Complexity: 11/100

Category: General

Source: https://github.com/x85446/claudecodetricks/tree/main/skills/pm-requirement

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