tactic-spec-brainstorm
Skill0 starsChanged 3 months agoMITView on GitHub
Refine OpenSpec exploration or an uncertain project idea into one focused, explicitly approved change, then generate, strictly validate, and review every planning artifact required for implementation. Use after openspec-explore or when the user wants to converge on an OpenSpec proposal without starting implementation; requires the OpenSpec CLI and an initialized project or registered store.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- more-with-lessSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- tactic-lean-orchestrateSkill
- tactic-spec-grillSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use references/workflow.md as the authoritative workflow.
- Distinctive: line 12
Before acting, resolve the OpenSpec project or registered store with the CLI.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OpenSpec Brainstorming
Use references/workflow.md as the authoritative workflow.
Remain in planning throughout the workflow. Do not write application code, scaffold implementation, or modify product files. Do not create an OpenSpec change until the user explicitly approves the change contract.
Before acting, resolve the OpenSpec project or registered store with the CLI. Ground claims in repository, specification, test, and configuration evidence; label assumptions instead of presenting them as facts. Never claim an artifact or repository write unless it was actually completed.
Complete when: one cohesive OpenSpec change has all artifacts transitively required for apply, passes strict validation and a cross-artifact coherence review, and has been presented for user review. The next action is user approval followed by the apply workflow, not implementation in this skill.
Subagent coordination
The main agent owns the change contract and all planning writes. Use the portable Scout contract only for bounded read-only repository research or independent artifact review. Scouts never create or edit proposal, specs, design, or tasks. When the required handoff would contain most of the planning context, keep the review direct.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

