Skip to content
Back to skills

spark-off

ASecurity

Exit CocoSpark brainstorm mode, optionally carry forward selected insights, and close the exploration session cleanly. Usage: $spark-off.

  • 724 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 5, 2026
ai-agents

Security analysis

A100/100

Pro scans all 18 files and shows the line behind each finding

Scanned June 5, 2026

npx -y skills add Snowflake-Labs/cocoplus --skill skills --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of spark-off?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for spark-off
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/snowflake-labs-spark-off/badge)](https://www.skillsdirectory.com/skills/snowflake-labs-spark-off)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "spark-off"
description: "Exit CocoSpark brainstorm mode, optionally carry forward selected insights, and close the exploration session cleanly. Usage: $spark-off."
version: "1.0.0"
author: "CocoPlus"
tags:
  - cocoplus
  - cocospark
---

Your objective is to conclude an active CocoSpark brainstorm session.

Before proceeding, verify that `.cocoplus/` exists.
If not: output "CocoPlus not initialized in this directory. Run `$pod init` to begin." Then stop.

If `.cocoplus/modes/coco-spark.on` does not exist:
- Output: "No active CocoSpark session found. Run `$spark` to start a brainstorm." Then stop.

## Exit Brainstorm Mode

1. Remove `.cocoplus/modes/coco-spark.on`
2. Offer: "Capture insights as notes? (yes/no)"
3. If yes:
   - Prompt: "What insights should be carried forward?"
   - If `.cocoplus/lifecycle/spec.md` exists, append a short `## Brainstorm Insights` section and create commit `docs(spec): added brainstorm insights`
   - If `spec.md` does not exist, append the notes to the active `.cocoplus/spark-[timestamp].md` file and do not create a lifecycle commit
4. If no: make no additional file changes

## Output

Output:
```
Brainstorm concluded.
[Insights captured | No changes made]
Ready for `$spec` when you are.
```

## Anti-Rationalization

| Shortcut / Temptation | Why It Fails |
|-----------------------|--------------|
| End spark mode without removing flag | Leaves session state inconsistent and confuses later commands |
| Auto-inject brainstorm notes into lifecycle artifacts | Conflates exploration with approved plan/spec decisions |
| Skip explicit yes/no capture prompt | Insight persistence becomes accidental and non-deterministic |

## Exit Criteria

- [ ] `.cocoplus/modes/coco-spark.on` flag is removed when a session is active
- [ ] If insights are captured and `spec.md` exists, a `## Brainstorm Insights` section is appended and commit `docs(spec): added brainstorm insights` is created
- [ ] If insights are captured and `spec.md` is absent, notes are appended to the active `.cocoplus/spark-[timestamp].md` file without lifecycle commit
- [ ] Output confirms brainstorm closure and next-step guidance toward `$spec`

Files in this skill

  • assist-mode/cocoplus-off.skill.md3.3 KB
  • assist-mode/cocoplus-on.skill.md4.1 KB
  • cocobehavior/SKILL.md3.8 KB
  • cocobloom/bloom-crystallize.skill.md4.8 KB
  • cocobloom/bloom-skip.skill.md1.3 KB
  • cocobloom/bloom.skill.md6.4 KB
  • cocobrew/build.skill.md4.1 KB
  • cocobrew/plan.skill.md6.9 KB
  • cocobrew/review.skill.md5.3 KB
  • cocobrew/ship.skill.md5.6 KB
  • cocobrew/spec.skill.md7.2 KB
  • cocobrew/test.skill.md3.1 KB
  • cocobrew/worktree-utils.md580 B
  • cococontext/context-add.skill.md5.3 KB
  • cococontext/context-list.skill.md2.4 KB
  • cococontext/context-view.skill.md1.8 KB
  • cococupper/cup-history.skill.md1.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…