oneshot
Skill68 starsChanged 4 months agoMITView on GitHub
Quick implementation without a full spec file
12 other projects use a version of this.
Adopted by
Most recently taken up by
- willink-oss/willink-claude-kittheir own version, first seen Nov 15, 2026
- NickolasBenakis/agent-playbooktheir own version, first seen Nov 15, 2026
- ADWilkinson/astacktheir own version, first seen Nov 8, 2026
- scalation-ai/oneshottheir own version, first seen Nov 1, 2026
- coroboros/agent-skillstheir own version, first seen Oct 29, 2026
- 2bTwist/dotagentstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use brainstorm.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- NickolasBenakis/agent-playbook★ 5same name
- coroboros/agent-skills★ 4same name
- GlamgarOnDiscord/claude-saas-blueprint★ 2same name
- scalation-ai/oneshot★ 2same name
- ADWilkinson/astack★ 1same name
- corygabrielsen/skills★ 1same name
- 2bTwist/dotagents★ 0same name
- codebyalexx/claude-skills★ 0same name
- TheWatcher01/skills★ 0same name
- TheYMK/agent-skills★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 17 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
17
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
After clarification: ensure you understand exactly what to build
- Distinctive: line 26
After exploration results: reflect on completeness before planning
- Distinctive: line 27
Before implementation: consider edge cases, patterns to follow, potential issues
- Distinctive: line 28
After validation: ensure the approach aligns with user intent
- Distinctive: line 34
Use AskUserQuestion to clarify before exploration:
- Distinctive: line 38
Default values for new fields?
- Distinctive: line 55
Do not proceed until critical details are clarified.
- Distinctive: line 66
No ceiling, real floor: Use at least 2 agents per domain in scope (1 only for a genuinely trivial single-file change).
- Distinctive: line 95
Add one agent per distinct table cluster, or to cover prod alongside dev.
- Distinctive: line 111
After agents return, verify coverage across all dimensions:
- Very specific: line 114
Similar patterns identified?: Do I have a reference implementation to follow?
- Very specific: line 116
Library docs sufficient?: If not -> launch additional parallel explore-docs agents
- Distinctive: line 118
Do NOT proceed with incomplete context.
- Distinctive: line 124
Write detailed implementation plan:
- Distinctive: line 150
Ask with AskUserQuestion: "Approve this plan?"
- Distinctive: line 163
Follow patterns from exploration
- Distinctive: line 180
Tests are MANDATORY: all existing tests must pass (zero regressions).
- Distinctive: line 188
VALIDATE: - always ask before implementing
- Distinctive: line 189
STAY IN SCOPE: - only what's needed
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YOU ARE EXECUTING THE /oneshot SKILL. The user triggered this skill. Follow ALL instructions below step by step. Do NOT treat this as a freeform conversation - execute the skill workflow.
Follow CLAUDE.md rules.
Ultra Think Strategy
Ultra think before each phase transition:
- After clarification: ensure you understand exactly what to build
- After exploration results: reflect on completeness before planning
- Before implementation: consider edge cases, patterns to follow, potential issues
- After validation: ensure the approach aligns with user intent
1. CLARIFY REQUIREMENTS
Use AskUserQuestion to clarify before exploration:
Must clarify (if not specified)
- Error messages for user-facing failures?
- Default values for new fields?
- Validation rules?
- What triggers state changes?
UX Decisions (if not specified)
- What happens on success? (toast, redirect, refresh?)
- What happens on error?
- Confirmation dialogs needed?
Permissions (if not specified)
- Who can perform each action?
- RLS policy rules (if the DB uses RLS)?
Scope (if not specified)
- Backend only, frontend only, or both?
- Database changes needed?
Do not proceed until critical details are clarified.
2. EXPLORE (PARALLEL)
Launch focused agents in a single message (parallel execution). There is no upper limit on agent count. Spawn one agent per distinct concern, area, or file-cluster the task actually has, and scale up freely with its breadth. The lists below are a starting menu, not a quota: add as many agents as full coverage requires.
Agent-count principle
- You decide the count from the actual scope. Assess how many distinct concerns / areas / file-clusters the task really spans on this codebase, and launch one focused agent for each. Do not anchor to a fixed number or to file counts.
- No ceiling, real floor. Use at least 2 agents per domain in scope (1 only for a genuinely trivial single-file change). Above that floor there is no maximum; on a large codebase the realistic count usually sits well above it.
- One distinct focus per agent. Split by concern so two agents never run the same search. Add agents to widen coverage, never to duplicate it.
- No batching. Launch them all in one message; the harness schedules them, so you never hold back to stay under a number.
Backend Agents (≥2 when backend in scope, one per distinct concern, no maximum)
- Domain & data flow -
explore-codebase: "Find entities, repository interfaces, value objects, and DTOs related to [feature] in backend/internal/domain/ and backend/internal/application/dto/" - Usecases & business logic -
explore-codebase: "Find usecases related to [feature] in backend/internal/application/usecases/. Read their Execute methods, dependencies, and error handling" - Handlers & routing -
explore-codebase: "Find HTTP handlers and routes related to [feature] in backend/internal/presentation/. Check middleware, validation, response patterns" - Infrastructure & services -
explore-codebase: "Find repo implementations, external service adapters, and config related to [feature] in backend/internal/infrastructure/" - Similar patterns -
explore-codebase: "Find the most similar existing feature to [feature] in backend/. I need to replicate its patterns"
Frontend Agents (≥2 when frontend in scope, one per distinct concern, no maximum)
- Components & UI -
explore-codebase: "Find components related to [feature] in frontend/src/components/. Check props, state, Shadcn UI usage" - Hooks & state -
explore-codebase: "Find hooks, React Query calls, and state management related to [feature] in frontend/src/hooks/ and frontend/src/lib/" - Pages & routing -
explore-codebase: "Find pages and layouts related to [feature] in frontend/src/app/. Check route structure, data fetching, i18n" - Types & API layer -
explore-codebase: "Find TypeScript types, API client functions related to [feature] in frontend/src/types/ and frontend/src/lib/" - Similar patterns -
explore-codebase: "Find the most similar existing feature to [feature] in frontend/src/. I need to replicate its patterns"
The supporting agents below fan out the SAME way as the code agents: one agent per distinct concern, no maximum. None of them is capped at a single instance.
Database Agents (≥1 when DB in scope, one per distinct concern, no maximum)
Launch one explore-db per distinct DB concern in the same single message. First token of each prompt selects the env (dev/prod, defaults to dev).
- Schema & relationships -
explore-db: "dev - Map tables and foreign keys related to [feature]: columns, types, FK relationships" - Constraints & policies -
explore-db: "dev - Inspect constraints and RLS policies (if used) on tables related to [feature]"
Add one agent per distinct table cluster, or to cover prod alongside dev.
Documentation Agents (≥1 when external docs needed, one per library/feature, no maximum)
- [library A] -
explore-docs: "[library A] [specific feature] documentation" - [library B] -
explore-docs: "[library B] [specific feature] documentation"
Web-research Agents (≥1 when external research needed, one per topic, no maximum)
- [topic A] -
websearch: "[topic A] best practices 2025 2026" - [topic B] -
websearch: "[topic B] ..."
2.5 POST-EXPLORATION CHECK
After agents return, verify coverage across all dimensions:
- Full code path traced? Can I trace handler -> usecase -> repository -> DB (backend) and page -> hook -> API -> component (frontend)? If gaps -> launch targeted
explore-codebase - Similar patterns identified? Do I have a reference implementation to follow? If not -> launch
explore-codebase - Data model complete? Tables, columns, relationships, policies known? If not -> launch additional parallel
explore-dbagents - Library docs sufficient? If not -> launch additional parallel
explore-docsagents
Do NOT proceed with incomplete context.
3. PLAN
Write detailed implementation plan:
## Implementation Plan
### Database changes (if applicable)
- Migration: [description]
### Backend changes
- Files to create/modify with line numbers
### Frontend changes
- Files to create/modify with line numbers
### Patterns to follow (from exploration)
- [code snippets to replicate]
### Order
1. [step 1]
2. [step 2]4. VALIDATE
Ask with AskUserQuestion: "Approve this plan?"
- "Implement"
- "Modify"
5. IMPLEMENT
After validation, implement:
- Backend first (Domain -> Application -> Infrastructure -> Presentation)
- Frontend second (Types -> API -> Hooks -> Components -> Pages)
Rules:
- Follow patterns from exploration
- No hardcoded values
- Complete error handling
useTranslationsfromnext-intlfor ALL user-facing text; Shadcn UI for standard components; strict TypeScript (noany)- Write unit tests for new usecases/services (backend
*_test.go) and for new components with branching logic, new hooks, and new utility/parser functions (frontend*.test.ts/*.test.tsx). Follow existing test patterns; cover happy path + main error cases
For significant UI: Skill(skill="frontend-design:frontend-design")
6. VERIFY
cd backend && go build ./... && go vet ./... && golangci-lint run ./... && go test ./...
cd frontend && npm run test:run && npm run buildTests are MANDATORY: all existing tests must pass (zero regressions). Fix any failure before proceeding.
Rules
- CLARIFY FIRST - understand requirements before exploring
- EXPLORE SECOND - parallel exploration before planning
- VALIDATE - always ask before implementing
- STAY IN SCOPE - only what's needed
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.

