@bonesofspring/ai-rules 0.2.20 → 0.2.22

package/presets/claude/go/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic — in **`task-continue.md`**.
-
-## Short form
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/go/commands/feature-start.md

@@ -1,38 +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 agent command
-
-Starts the **analysis phase** for a new task. For new work, prefer `/task` because it builds a dynamic pipeline via `task-router` first.
-
-## What to do
-
-1. Extract the task description from command arguments (everything after `/feature-start`).
-2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
-3. Create `.claude/team/tasks/<slug>/` if it does not exist — via Write / Edit, not Shell `mkdir`.
-4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Invoke subagent **task-analyst** with the full task description and artifact paths.
-6. Wait for the analyst to finish. **Do not invoke 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: `/feature-continue <slug>` or `/task-continue <slug>`.
-
-## If slug already exists
-
-- If `status.json` is `awaiting_approval` — offer review or `/feature-continue`.
-- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/ios-swift/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic is in **`task-continue.md`**.
-
-## Short version
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/ios-swift/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 chooses roles and order automatically.
-
-Starts the **analysis phase** without the router. The parent agent acts as orchestrator (see `tooling-and-review/agent-team-orchestrator.md`).
-
-## 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 `.claude/team/tasks/<slug>/` if it does not exist yet — via **Write** of an artifact (not Shell `mkdir`).
-4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Optional: 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 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` — offer review or continue.
-- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/java/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic — in **`task-continue.md`**.
-
-## Short form
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/java/commands/feature-start.md

@@ -1,38 +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 agent command
-
-Starts the **analysis phase** for a new task. For new work, prefer `/task` because it builds a dynamic pipeline via `task-router` first.
-
-## What to do
-
-1. Extract the task description from command arguments (everything after `/feature-start`).
-2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
-3. Create `.claude/team/tasks/<slug>/` if it does not exist — via Write / Edit, not Shell `mkdir`.
-4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Invoke subagent **task-analyst** with the full task description and artifact paths.
-6. Wait for the analyst to finish. **Do not invoke 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: `/feature-continue <slug>` or `/task-continue <slug>`.
-
-## If slug already exists
-
-- If `status.json` is `awaiting_approval` — offer review or `/feature-continue`.
-- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/mcp-ts/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Preferred:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic lives in **`task-continue.md`**.
-
-## Short version
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Call the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/mcp-ts/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)
-
-> **Preferred:** `/task <description>` — the router picks roles and order automatically.
-
-Starts the **analysis phase** without the router. The parent agent acts as orchestrator (see `rules/tooling-and-review/agent-team-orchestrator.md`).
-
-## What to do
-
-1. Extract the task description from command arguments (everything after `/feature-start`).
-2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
-3. Create `.claude/team/tasks/<slug>/` if it does not exist yet — via Write / Edit (not Shell `mkdir`).
-4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Optionally: minimal `pipeline.json` with fixed steps (analyst → developer → reviewer → qa-tester).
-6. Invoke subagent **task-analyst** with the full task description and artifact paths.
-7. Wait for the analyst to finish. **Do not invoke 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 slug already exists
-
-- If `status.json` is `awaiting_approval` — offer review or continue.
-- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/next/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic — in **`task-continue.md`**.
-
-## Short form
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/next/commands/feature-start.md

@@ -1,38 +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 agent command
-
-Starts the **analysis phase** for a new task. For new work, prefer `/task` because it builds a dynamic pipeline via `task-router` first.
-
-## What to do
-
-1. Extract the task description from command arguments (everything after `/feature-start`).
-2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
-3. Create `.claude/team/tasks/<slug>/` if it does not exist — via Write / Edit, not Shell `mkdir`.
-4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Invoke subagent **task-analyst** with the full task description and artifact paths.
-6. Wait for the analyst to finish. **Do not invoke 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: `/feature-continue <slug>` or `/task-continue <slug>`.
-
-## If slug already exists
-
-- If `status.json` is `awaiting_approval` — offer review or `/feature-continue`.
-- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/nuxt/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic — in **`task-continue.md`**.
-
-## Short form
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/nuxt/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 `rules/tooling-and-review/agent-team-orchestrator.md`).
-
-## 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 `.claude/team/tasks/<slug>/` if it does not exist yet — via **Write** of an artifact (not Shell `mkdir`).
-4. Write `.claude/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.

package/presets/claude/php-hexagonal/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic — in **`task-continue.md`**.
-
-## Short form
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/php-hexagonal/commands/feature-start.md

@@ -1,38 +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 agent-team command
-
-Starts the **analysis phase** for a new task. For new work prefer `/task`, because it builds a dynamic pipeline through `task-router` first.
-
-## What to do
-
-1. Extract the task description from command arguments (everything after `/feature-start`).
-2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
-3. Create `.claude/team/tasks/<slug>/` if it does not exist yet — by writing a file (Write / Edit), not Shell `mkdir`.
-4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Invoke subagent **task-analyst** with the full task description and artifact paths.
-6. Wait for the analyst to finish. **Do not invoke 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: `/feature-continue <slug>` or `/task-continue <slug>`.
-
-## If slug already exists
-
-- If `status.json` is `awaiting_approval` — offer review or `/feature-continue`.
-- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/php-laravel/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic — in **`task-continue.md`**.
-
-## Short form
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/php-laravel/commands/feature-start.md

@@ -1,38 +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 agent-team command
-
-Starts the **analysis phase** for a new task. Prefer `/task` for new work because it builds a dynamic pipeline via `task-router` first.
-
-## What to do
-
-1. Extract the task description from command arguments (everything after `/feature-start`).
-2. Generate a **slug** (kebab-case, up to 48 characters) from the task title.
-3. Create `.claude/team/tasks/<slug>/` if it does not exist yet — via Write / Edit, not Shell `mkdir`.
-4. Write `.claude/team/active-task.json` → `{ "slug": "<slug>" }`.
-5. Invoke subagent **task-analyst** with the full task description and artifact paths.
-6. Wait for the analyst to finish. **Do not invoke 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: `/feature-continue <slug>` or `/task-continue <slug>`.
-
-## If slug already exists
-
-- If `status.json` is `awaiting_approval` — offer review or `/feature-continue`.
-- If the task is in progress — ask whether to continue or start a new slug.

package/presets/claude/svelte/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic — in **`task-continue.md`**.
-
-## Short form
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/claude/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 `rules/tooling-and-review/agent-team-orchestrator.md`).
-
-## 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 `.claude/team/tasks/<slug>/` if it does not exist yet — via **Write** of an artifact (not Shell `mkdir`).
-4. Write `.claude/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.

package/presets/cursor/android-kotlin/commands/feature-continue.md

@@ -1,23 +0,0 @@
----
-name: feature-continue
-description: Legacy alias for /task-continue that resumes a feature pipeline after human approval or pause.
----
-
-# Feature continue — legacy alias
-
-> **Prefer:** `/task-continue <slug>` — same behavior, respects `pipeline.json`.
-
-Continue after a human gate. Full logic is in **`task-continue.md`**.
-
-## Short version
-
-1. Read `pipeline.json` (if present) and `status.json`.
-2. Clear `awaitingHumanGate`; determine the next step from `pipelineIndex`.
-3. Invoke the subagent for `currentAgent`.
-4. The hook continues the chain when `autoChain: true`.
-
-See `task-continue.md` for details and the handoff table.
-
-## Product specs (docs/specs)
-
-When the next agent is **feature-developer** (or other implementer): if `docs/specs/INDEX.md` exists, instruct them to load **`product-specs`** and honor **Related specs** from `brief.md` (behavior SoT). Soft-fail on miss; never invent product behavior. No-op if INDEX is absent.

package/presets/cursor/android-kotlin/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 chooses 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. Optional: 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 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` — offer review or continue.
-- If the task is in progress — ask whether to continue or start a new slug.