workflow-index

Included with Lifetime

$97 forever

Use this skill at the start of any non-trivial work in a project that uses the requirements-framework. It maps the current phase to the single next command to run. Triggers on "what next", "where am I", "/req", or when the user is uncertain what workflow to use.

General

What this skill does


# Workflow Index

The requirements-framework runs your project through an ordered phase pipeline. At any moment the project is in exactly one phase, derived from requirement state.

**The phase order is configured per project** via the `workflow:` config section, so the number, names, and order of phases can differ from the default map below. Do not hardcode the pipeline. The authoritative runtime resolution is:

- **`/req`** — the conductor. It resolves the current phase *and* the skill that phase dispatches to, live from the project's config, then routes you. When unsure what to run, just run `/req`.
- **`req status`** — shows the current requirement state the phase is derived from.

```bash
req status            # short
req status --verbose  # full requirement table
```

## Default (zero-config) workflow — fallback reference

This is the **built-in default** that applies when a project has no `workflow:` section. Use it as a mental model only; a configured project may reorder, rename, or add phases, and `/req` always wins over this table.

| Phase | When | Run |
|-------|------|-----|
| design | `design_approved` unsatisfied | `/brainstorm` |
| plan-write | `plan_written` unsatisfied | `/write-plan` |
| plan-validate | `solid_reviewed` unsatisfied (after plan_written) | `/arch-review` |
| implement | `verification_evidence` unsatisfied | `/execute-plan` |
| review | `pre_pr_review` unsatisfied | `/deep-review` then `/codex-review` |
| refactor | (manual) when a large refactor is needed | `/refactor-orchestrate` |
| ship | all session requirements satisfied | finalize commits + PR |

In the default workflow, planning is split because two skills are needed to clear all planning gates: `/write-plan` produces a plan (flips `plan_written`), and `/arch-review` validates it (flips `commit_plan`, `adr_reviewed`, `tdd_planned`, `solid_reviewed`).

## Common transitions (default workflow)

- After `/brainstorm` → `design_approved` flips → next phase: **plan-write**
- After `/write-plan` → `plan_written` flips → next phase: **plan-validate**
- After `/arch-review` → 4 planning requirements flip → next phase: **implement**
- After `/deep-review` → `pre_pr_review` flips → next phase: **ship**

## How to use this index

1. Prefer `/req` — it reads the project's configured workflow and routes for you.
2. If reasoning by hand, read the user's recent prompt and `req status`, then identify the *next* unsatisfied gate along the configured pipeline (the default map above when the project is zero-config).
3. Recommend (or invoke) the matching command for that phase.
4. If multiple phases look open, default to the earliest one — the pipeline runs top-to-bottom.

This skill is *read-only*: it teaches the map but does not move the project. To act on the map, run `/req` (the conductor command that auto-dispatches the configured skill) or invoke the matching command directly.

Files: 2

Size: 6.4 KB

Complexity: 17/100

Category: General

Source: https://github.com/harmaalbers/claude-requirements-framework/tree/main/plugins/requirements-framework/skills/workflow-index

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