feature-state

Included with Lifetime

$97 forever

Change a feature's state (active/paused/replaced/abandoned). Use when a feature needs to be paused while waiting on something, marked obsolete because another feature replaces it, or abandoned because it won't be pursued. Requires companion fields for non-active states.

General

What this skill does


# Change Feature State

You are executing the **CHANGE STATE** workflow — flipping the `state:` field in a feature's `idea.md` frontmatter and validating the required companion fields.

## Arguments

`$ARGUMENTS`: `<feature-id> <state> [--reason "..."] [--replaced-by <id>]`

Examples:
- `/feature-state user-roles paused --reason "Waiting on auth team"`
- `/feature-state old-feature replaced --replaced-by new-feature`
- `/feature-state nice-to-have abandoned --reason "Out of scope"`
- `/feature-state stuck-feature active` (resume from paused/tombstone)

## Step 1: Parse Arguments

Extract:
- `<feature-id>` — required
- `<state>` — one of `active`, `paused`, `replaced`, `abandoned`
- `--reason "..."` — used for `paused` (writes `pausedReason`) or `abandoned` (writes `abandonedReason`)
- `--replaced-by <id>` — used for `replaced` (writes `replacedBy`)

If arguments are missing or malformed, show usage and stop.

## Step 2: Load Feature

Read `docs/features/<feature-id>/idea.md`. If it doesn't exist, error:
> "No feature `<feature-id>`. Check `docs/features/` or run `/feature-search`."

If `shipped.md` exists AND the requested new state is `replaced` or `abandoned`, refuse:
> "`<feature-id>` is already shipped — tombstoning it makes no sense. If it needs to be reverted, revert the PR and remove `shipped.md` first."

## Step 3: Validate Required Companions

| Target state | Required argument |
|---|---|
| `paused` | `--reason "..."` |
| `replaced` | `--replaced-by <id>` |
| `abandoned` | `--reason "..."` |
| `active` | none |

If the required companion is missing, ask the user for it via AskUserQuestion before proceeding.

For `replaced`: also check that the referenced ID has an `idea.md` on disk. If not, warn but allow (forward reference).

## Step 4: Update Frontmatter

Use the Edit tool to update `docs/features/<feature-id>/idea.md`:

1. **Set `state:`** — replace any existing `state:` line, or insert one after `id:`.
2. **Set companion field** — same insertion pattern.
3. **Clean up obsolete companions** when state changes:
   - Resuming to `active` from `paused`: remove `pausedReason:`
   - Resuming to `active` from `replaced`: remove `replacedBy:`
   - Resuming to `active` from `abandoned`: remove `abandonedReason:`

Do NOT touch any other frontmatter or content.

## Step 5: Confirm + Regen Dashboard

The PostToolUse hook will regenerate `DASHBOARD.md` automatically when you edit `idea.md`.

Print a one-line confirmation:
> "✓ `<feature-id>` is now `<state>`. <Companion field summary>"

## Step 6: Suggest Follow-Up

| New state | Suggest |
|---|---|
| paused | "When the blocker clears, run `/feature-state <id> active` to resume." |
| replaced | "If `<replaced-by-id>` doesn't exist yet, run `/feature-capture` to create it." |
| abandoned | (none — terminal state for now) |
| active (from paused) | "Resume with `/feature-implement <id>` or `/feature-autopilot <id>`." |

## Notes

- This is the only correct way to tombstone a feature. Do NOT delete the directory — the history is the whole point.
- The dashboard hook regenerates on edit; no manual regen needed.
- State changes are reversible. Going `paused → active → paused` is fine.

Files: 1

Size: 3.5 KB

Complexity: 13/100

Category: General

Source: https://github.com/schuettc/claude-code-plugins/tree/main/feature-workflow/skills/feature-state

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