@bonesofspring/ai-rules 0.2.20 → 0.2.21

package/presets/cursor/svelte/commands/feature-start.md

@@ -1,41 +0,0 @@
----
-name: feature-start
-description: Legacy analyst-only feature intake. Prefer /task for new work because it uses router and dynamic pipeline.
----
-
-# Feature start — legacy (analyst only)
-
-> **Prefer:** `/task <description>` — the router picks roles and order automatically.
-
-Starts the **analysis phase** without the router. The parent agent acts as orchestrator (see `agent-team-orchestrator.mdc`).
-
-## What to do
-
-1. Extract the task description from the command arguments (everything after `/feature-start`).
-2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
-3. Create `.cursor/team/tasks/<slug>/` if it does not exist yet — via **Write** of an artifact (not Shell `mkdir`).
-4. Write `.cursor/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Optionally: a minimal `pipeline.json` with fixed steps (analyst → developer → reviewer → qa-tester).
-6. Invoke subagent **task-analyst** (Task tool) with the full task description and artifact paths.
-7. Wait for the analyst to finish. **Do not invoke the developer** at this stage.
-
-## Product specs (docs/specs)
-
-When invoking **task-analyst**: if `docs/specs/INDEX.md` exists, instruct consume via **`product-specs`** and cite **Related specs**. Soft-fail on miss; never invent behavior.
-
-If the user/AC requests generation or bootstrap, or INDEX is missing **with** bootstrap AC / `/spec-start` intent: instruct **author mode** inside the same analyst step — load **`product-specs-authoring`** + skill **`spec-authoring`**. Authoring is **not** a separate pipeline agent. Handoff must list created paths + INDEX diff; human gate must approve generated specs before feature-developer.
-
-
-## Human gate
-
-After the analyst:
-
-- Show the user links to `brief.md` and `decomposition.md`.
-- Also ask them to check **Related specs** in `brief.md` when `docs/specs/INDEX.md` exists.
-- Ask them to review and approve or send edits.
-- To continue: `/task-continue <slug>` or `/feature-continue <slug>`.
-
-## If the slug already exists
-
-- If `status.json` is `awaiting_approval` — suggest review or continue.
-- If the task is in progress — ask whether to continue or start a new slug.