/spectre-feature-root

Internal initializer for a missing Spectre feature root. Invoke only from a standalone workflow with no confirmed managed root. Do NOT invoke for existing roots, orchestrated calls missing a root, or direct user requests.

BOOST

joenandez@joenandez

GitHub

From plugin

spectre

16521 skills8 agents

Install

$ npx -y skills add joenandez/spectre --skill spectre-feature-root --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/spectre-feature-root

Context preview

The summary Claude sees to decide when to auto-load this skill.

Internal initializer for a missing Spectre feature root. Invoke only from a standalone workflow with no confirmed managed root. Do NOT invoke for existing roots, orchestrated calls missing a root, or direct user requests.

SKILL.md

spectre-feature-root.SKILL.md

name: "spectre-feature-root"
description: "Internal initializer for a missing Spectre feature root. Invoke only from a standalone workflow with no confirmed managed root. Do NOT invoke for existing roots, orchestrated calls missing a root, or direct user requests."
user-invocable: false

feature-root

Purpose

Create a canonical root with no naming/reuse gate.

Inputs

Work/name hint; `KIND=feature|bug` (default `feature`); repo-relative candidate; write authority.

Working Set

Read exact candidates/ignore state only; never select existing work.

Outputs + DONE

Return `FEATURE`, repo-relative `FEATURE_ROOT`, warnings. DONE: valid root, neutral marker, tenancy, no phase artifact.

Method / guardrails

1. Use an explicit caller candidate/descendant. Reject absolute, traversal, symlink-escaping, or unmanaged paths. 2. Otherwise derive a concise kebab name and choose the first free `.spectre/{features|bugs}/<name>[-N]/` per `KIND`. Never inspect or offer existing roots, ask whether to reuse one, present naming options, or wait for approval; suffixes resolve collisions. 3. Create `feature.json` containing only `schema_version`, `created_at`, `feature`, and repo-relative `feature_root`; no lifecycle, alias, branch, or absolute path. 4. Unless `.spectre/` is ignored, preserve `.spectre/.gitignore`; require literal `manifest.json`, `bin/`, `handoffs/`, `!features/`, `!bugs/`, plus `evidence/`, `checkpoints/`, `runs/`, `markers/`, `working_set.json`, `cleanup_summary.md`, `execution_state.md`, `reviews/task_review_attempt.json`, `reviews/task_review_safety.json` under both `features/**/` and `bugs/**/`. Specs/research/decisions/reviews/proof stay trackable. Never edit root `.gitignore`; warn on local-only matches. 5. Write only root initialization.