spectra-ingest

Featured

Update an existing Spectra change from external context

Testing & QA 45 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

Update an existing Spectra change — from a plan file or conversation context. **Plan file support** is available when the tool has a plan directory (`.cursor/plans/`). Otherwise, use conversation context to update artifacts. **Prerequisites**: This skill requires the `spectra` CLI. If any `spectra` command fails with "command not found" or similar, report the error and STOP. **Input**: Optionally specify a plan file path or name. - `/spectra:ingest .cursor/plans/agile-discovering-rocket.md` - `/spectra:ingest agile-discovering-rocket` - `/spectra:ingest` (use conversation context or auto-detect plan file) **Steps** 1. **Locate the requirement source** a. **Argument provided** → treat as plan file reference (prepend `.cursor/plans/` and append `.md` if needed) - If the file exists → use it as the plan file source, proceed to Step 2 - If the file does NOT exist → report the error and **stop** b. **No argument, plan file detectable**: - Check conversation context for plan file path (plan mode system messages include the path like `.cursor/plans/<name>.md`) - If found and the file exists → use the **AskUserQuestion tool** to ask: - Option 1: Use the plan file - Option 2: Use conversation context - If the user picks plan file → proceed to Step 2 - If the user picks conversation context → skip Step 2, go to Step 3 c. **No argument, no plan file detectable**: - Check `.cursor/plans/` for recent files - If recent files exist → list ...

Details

Author
YuDefine
Repository
YuDefine/nuxt-supabase-starter
Created
7 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category