strategy-specification

Included with Lifetime

$97 forever

Specification-workflow patterns (input assessment, produce-then-validate, gap-informed revision) consumed by the State Analyst alongside strategy-core for targeted Supervisor briefings.

General

What this skill does

# Strategy: Specification

Workflow-specific patterns for the specification workflow. Consumed by the State Analyst alongside `strategy-core` to produce targeted Supervisor briefings.

## Goal

Produce a validated feature specification where the advocate verdict is `ready`.

## Success Criteria

- `spec.md` exists with user stories and functional requirements
- `advocate-report.md` verdict: `ready`

## Patterns

### Input Assessment

Sparse input (missing Who/Problem/Value) typically benefits from enrichment before analysis. Detailed input with clear problem framing can go directly to the analyst. Consider the domain context — a sparse input in a well-understood domain may not need enrichment if the analyst can infer context from existing artifacts (constitution, codebase analysis).

**Rationale**: Enrichment adds a full interaction round with the user. When the input already contains sufficient signal, skipping enrichment saves time without sacrificing quality. The analyst is capable of working with moderately detailed input.

### Produce-then-Validate

The primary pattern is: an agent produces an artifact, then a different agent (or gate) validates it. For specification, this means the analyst produces `spec.md`, the advocate reviews it. Resist the urge to skip validation even when the analyst report looks comprehensive.

**Rationale**: Self-review is unreliable. The analyst's blind spots are systematic — a separate reviewer with adversarial framing catches what the producer cannot see in their own work.

### Gap-Informed Revision

When the advocate identifies gaps, the next analyst pass should be informed by those specific gaps. The analyst should see what was flagged and focus revision effort there, not rewrite the entire spec. Use informed-by edges to carry gap context forward.

**Rationale**: Unfocused revision wastes effort on sections that were already adequate, and may introduce new issues in previously-clean areas. Targeted revision converges faster.

### Research Before User

When gaps are knowledge-based (factual unknowns about the codebase, existing protocols, technical constraints), targeted research often resolves them faster than asking the user. Try research first; escalate to user only if research is inconclusive or the question is genuinely about preference.

**Rationale**: Users should not be asked questions that the codebase can answer. Research is faster and more precise for factual questions. Reserve user interaction for genuine decisions.

## Anti-Patterns

- **Post-pass-1 enrichment**: Running enrichment after pass 1 — input is already established and enrichment adds no value
- **Uniform gap treatment**: Treating all gaps identically — knowledge, preference, and scope gaps need different responses
- **User-for-researchable**: Asking the user about things that could be researched from the codebase or documentation
- **Recurring-gap iteration**: Continuing to iterate when the advocate keeps flagging the same gaps across passes

## Guardrails

- Constitution must exist before specification work begins (INV-002)
- After 5 passes, surface the situation to the user with options (INV-004)
- Never skip the advocate gate — every analyst output must be validated

Files: 1

Size: 3.4 KB

Complexity: 7/100

Category: General

Source: https://github.com/deepeshbodh/human-in-loop/tree/main/plugins/humaninloop/skills/strategy-specification

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