Ccs Align
thedotmack/claude-mem
Run the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → getobservations, land them in a seat-owned middle…
Create a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight.
$ npx skills add joenandez/spectre --skill spectre-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install joenandez/spectre spectre-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/spectre/skills/spectre-plan .claude/skills/spectre-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spectre-plan" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-plan into .claude/skills/spectre-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add joenandez/spectre --skill spectre-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install joenandez/spectre spectre-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/spectre/skills/spectre-plan .agents/skills/spectre-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spectre-plan" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-plan into .agents/skills/spectre-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add joenandez/spectre --skill spectre-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install joenandez/spectre spectre-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/spectre/skills/spectre-plan .cursor/skills/spectre-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spectre-plan" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-plan into .cursor/skills/spectre-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/joenandez/spectre.git --path plugins/spectre/skills/spectre-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add joenandez/spectre --skill spectre-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install joenandez/spectre spectre-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/spectre/skills/spectre-plan .gemini/skills/spectre-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spectre-plan" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-plan into .gemini/skills/spectre-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install joenandez/spectre spectre-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add joenandez/spectre --skill spectre-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/spectre/skills/spectre-plan .github/skills/spectre-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spectre-plan" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-plan into .github/skills/spectre-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add joenandez/spectre --skill spectre-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install joenandez/spectre spectre-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/spectre/skills/spectre-plan .opencode/skills/spectre-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spectre-plan" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-plan into .opencode/skills/spectre-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
spectre-planCreate a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight.
Spectre Plan is an agent skill from joenandez/spectre. Create a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight. Do not use for scoping, bug diagnosis, read-only work, or execution of approved artifacts.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/create-plan.md`, `references/estimation-guidance.md` and `references/high-level-design-gate.md`).
The repository describes itself as: Spectre is a battle-tested 6 stage agentic engineering workflow for building complex, production-ready features. You stay in the loop for the decisions that matter. Your agents…. The licence is MIT.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 931c9e8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Spectre Plan loads about 1.7k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 742 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from joenandez/spectre at commit 931c9e8, republished under its MIT licence (© joenandez). 742 words, ~1,675 tokens.
.claude/skills/spectre-plan/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Turn confirmed Scope into the smallest draft and handoff. spectre-plan-route classifies; primary owns plan. Scope remains immutable.
$ARGUMENTS: confirmed Scope—thread or managed root/descendant. Repository changes without Scope return to spectre-scope; bugs use spectre-fix. Read-only diagnosis/review, release, and approved-artifact execution remain direct.ux.md (preferred) or legacy specs/ux.md, task_context.md, and prior plans.FEATURE_ROOT only when explicit/current-thread evidence ties it to this work (physical directory wins; never branch/recency/lifecycle/scans); distinct work ignores ambient roots. Otherwise, including on collision, standalone MUST first load and follow @skill-spectre:spectre-feature-root through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged.concepts/scope.md when present, else confirmed thread; never change it without explicit scope-change approval.references/estimation-guidance.md when applicable; each estimate excludes waits and never delays or blocks the gate.--tag, assess previews, then exact-load applicable matches; never guessed loads. Refine only for an unresolved question or new subject. Keep IDs/revisions in task_context.md; previews/unloaded candidates are not evidence.Every route writes specs/plan.md and task_context.md with Scope/authority-bound ## Minimum Solution Selection; no review/task/index/task-review artifacts.
DONE when task_context.md binds initial/observed routing to draft/authority hashes; Scope is unchanged; plan.completed records draft; handoff gives alignment/Trade-offs; telemetry is complete|degraded, or authority/scope stops it.
Child skill DONE is internal: resume the next Plan step in this turn. Only Plan's own handoff or escalation ends it.
spectre-ux; load-bearing interaction/layout validation routes to spectre-prototype.Skill(spectre-plan-route) in initial mode. Never print its record; its DONE and limits end at the record. In the same response, run spectre-workflow plan start with root/scope hash, record, size/route, reasons, design/probe flags, boundaries; retain PLAN_RUN_ID for plan.started. Report size/rationale in one progress line beside that call; continue to step 3.@spectre:finder, @spectre:analyst, or @spectre:patterns; L/XL necessary dimensions. Live external captures belong to Execute, never Plan's evidence dispatch. Dispatch no dimension cited by path, knowledge ID/revision, or thread decision; evidence: SUFFICIENT with uncertainty below HIGH and full citation gathers locally at any size. The fresh evidence-only challenger is wave-independent: M triggers it for durable state, identity, public contract, migration, dependency, or workflow/lifecycle; L/XL always, with the wave or alone. Primary persists accepted evidence/IDs/revisions in task_context.md. @spectre:web-research only decides external API/framework. Refine knowledge search after affected files are known; load a work body only for a stated question, never reload an unchanged revision, and pass workers compact findings with provenance.references/minimum-solution.md after initial classification. From accepted evidence, select incumbent-first and persist ## Minimum Solution Selection in task_context.md, bound to Scope/authority/accepted evidence. XS/S decide locally; primary applies the canonical simpler-wins result.Skill(spectre-plan-route) in observed mode with completed selection before drafting; never print its record, and continue to step 6 in the same response. Plan automatically uses the observed route with no paid rerun or user tier gate unless Scope, explicit design, or authority conflicts.${CLAUDE_PLUGIN_ROOT}/skills/spectre-plan/references/create-plan.md with the observed route-mapped depth: XS → light --no-review --execution structured; S inherits it; M/L → standard --no-review --execution structured; XL → comprehensive --no-review --execution structured. Never review/task here. XS uses light, not xs, so no Execution Mode: direct.plan.reclassified with plan hash, records, regret. Append observed record to task_context.md with draft raw-byte hash plus Scope/authority hash; emit unchanged plan.completed artifact hashes/counts/planning elapsed. Telemetry failure is degraded and never blocks handoff.specs/plan.md derive requested outcome, approach, material decisions, Scope/anti-scope boundaries, credible risks, verification intent, and ordering/shared-contract constraints. Immediately before Execute show Trade-offs verbatim (None allowed): Execute accepts them; feedback revises the draft. On Scope change, selected-design conflict, missing irreversible decision, or unavailable authority, withhold the handoff. Otherwise return exactly one copy-ready fenced command: /spectre:spectre-execute <repo-relative plan.md> --origin plan --preflight-plan <xs|light|standard|comprehensive>. observed XS → xs; S → light; M/L → standard; XL → comprehensive. Launching that command is the user's alignment signal. Never pass --orchestrated or wait for delivery insurance.| Handoff | Details |
|---|---|
| 🧭 Current phase | Done |
| 📦 What was just done | Result |
| ▶️ Proposed next step | Render resolved action. |
Execute owns assessment/review/tasks/gates/resume. Never generate a goal prompt. Render Execute: resolved absolute plan path, --origin plan, resolved preflight depth.
© joenandez, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in plugins/spectre/skills/spectre-plan of joenandez/spectre.
Open the folder on GitHubat commit 931c9e8
Spectre Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spectre Plan this skilljoenandez/spectre | 164 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Ccs Alignthedotmack/claude-mem | 99k | — | ~6.1k | Automated safety check: Pass | Apache-2.0 | |
| Grounded CitationsNousResearch/hermes-agent | 252k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Bio Read Alignment Bowtie2 AlignmentGPTomics/bioSkills | 1.2k | 1 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Bio Read Alignment Star AlignmentGPTomics/bioSkills | 1.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Bio Read Alignment Hisat2 AlignmentGPTomics/bioSkills | 1.2k | 1 repos | ~3.8k | Automated safety check: Pass | MIT |
thedotmack/claude-mem
Run the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → getobservations, land them in a seat-owned middle…
NousResearch/hermes-agent
Attaches a numbered, URL-backed citation to every outside fact in an answer or document, rejecting quotes that aren't real.
GPTomics/bioSkills
Aligns DNA short reads to a reference with Bowtie2, choosing end-to-end (whole read must align) vs local (soft-clip read ends) mode and a sensitivity preset; the de-facto aligner for ChIP-seq…
GPTomics/bioSkills
Aligns RNA-seq reads to a genome with STAR, the fast splice-aware aligner whose splice-junction database (built from a GTF at sjdbOverhang = readlength-1) and two-pass mode set junction sensitivity…
GPTomics/bioSkills
Aligns RNA-seq reads to a genome with HISAT2, the splice-aware aligner whose hierarchical graph FM-index runs at roughly a quarter of STAR's memory (~7 GB for human), whose SNP/haplotype graph index…
aiming-lab/AutoResearchClaw
Best practices for LLM alignment techniques including RLHF, DPO, and instruction tuning.
joenandez/spectre
A skill your agent uses when validating that the Spectre plugin itself still works after ANY change to this repo — skills, prompts, agents, hooks, the CLI, the Codex mirror, or a release.
joenandez/spectre
A skill your agent uses when modifying the Codex SPECTRE install flow, SessionStart continuity, project skill syncing, registry injection, or Codex-specific runtime files.
joenandez/spectre
Save a quiet, branch-keyed session snapshot with continuity, active work, and optional task/todo state for automatic resume.
joenandez/spectre
User-invoked front door for durable capture. An agent skill from joenandez/spectre.
joenandez/spectre
Rewrite a verbose SPECTRE skill into a compact, contract-form Spectre skill proposal — clear on WHAT, silent on HOW — grounded in the spectre-light distillation and freedom-tier budget.
joenandez/spectre
Rewrite Spectre subagent definitions into compact, contract-driven agents with clear routing, least-privilege tools, output schemas, and an auditable rewrite trail.
Create a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight. Spectre Plan is an agent skill from joenandez/spectre. Create a repository-grounded aligned draft after confirmed Scope, present its concise alignment brief, and hand it to Execute preflight.
Spectre Plan fits situations like: execution of approved artifacts.
Run `npx skills add joenandez/spectre --skill spectre-plan -a claude-code`. Or copy the skill folder (plugins/spectre/skills/spectre-plan in joenandez/spectre) into .claude/skills/spectre-plan in your project. Claude Code loads it when a task matches its description.
Run `npx skills add joenandez/spectre --skill spectre-plan -a codex`. Or copy the skill folder (plugins/spectre/skills/spectre-plan in joenandez/spectre) into .agents/skills/spectre-plan in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add joenandez/spectre --skill spectre-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spectre-plan, .gemini/skills/spectre-plan, .github/skills/spectre-plan and .opencode/skills/spectre-plan in your project.
SKILL.md names no scripts, command-line tools or credentials: Spectre Plan is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Spectre Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Spectre Plan: Ccs Align (thedotmack/claude-mem, 99k stars), Grounded Citations (NousResearch/hermes-agent, 252k stars), Bio Read Alignment Bowtie2 Alignment (GPTomics/bioSkills, 1.2k stars) and Bio Read Alignment Star Alignment (GPTomics/bioSkills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
joenandez (a GitHub user) maintains it in joenandez/spectre, which has 164 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 2, 2026.
Source: joenandez/spectre on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.