speckit-tinyspec-tinyspec
Skill1 starsChanged 26 days agoMITView on GitHub
Generate a single lightweight spec file with context, plan, and tasks for small changes
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs-auditSkill
- north-starSkill
- root-causeSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- speckit-tinyspec-classifySkill
- speckit-tinyspec-implementSkill
- speckit-verify-tasks-runSkill
- speckit-verify-tasksSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Very specific: line 24
Verify a spec-kit project exists by checking for .specify/ directory
- Distinctive: line 25
Verify git is available and the project is a git repository
- Distinctive: line 26
Verify the user has described the change (if not, ask what they want to build)
- Distinctive: line 33
If the task seems too large, warn the user and suggest the full workflow
- Very specific: line 40
Generate tinyspec file: Create a single file at specs/tiny/{feature-name}.md with this structure:
≈ “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
TinySpec
Generate a single lightweight specification file for small tasks that don't warrant the full SDD workflow. Combines context, requirements, implementation plan, and tasks into one concise document — minimal overhead, maximum clarity.
User Input
$ARGUMENTSYou MUST consider the user input before proceeding (if not empty). The user describes the small change they want to make (e.g., "add a logout button to the navbar", "fix the date format in the invoice PDF", "add input validation to the signup form").
Prerequisites
- Verify a spec-kit project exists by checking for
.specify/directory - Verify git is available and the project is a git repository
- Verify the user has described the change (if not, ask what they want to build)
Outline
- Assess scope: Quickly evaluate whether this task is appropriate for tinyspec:
- Good fit: Single feature, bug fix, UI tweak, config change, small refactor — anything that touches 1-5 files and takes under ~1 hour
- Bad fit: Multi-module features, architectural changes, new services, database schema redesigns — recommend full
/speckit.specifyinstead - If the task seems too large, warn the user and suggest the full workflow
- Identify affected files: Scan the codebase to determine:
- Which files will be modified (list them explicitly)
- Which files provide context (imports, types, related components)
- Which test files will need updates
Generate tinyspec file: Create a single file at
specs/tiny/{feature-name}.mdwith this structure:# TinySpec: {Title} **Branch**: {current-branch or new-branch-name} **Date**: {YYYY-MM-DD} **Status**: draft **Complexity**: small ## North-star case - **Failure moved**: {stopped when it shouldn't | ran and produced garbage | ran but needed the owner} - **Number that shows it**: {the loop-health / scorecard read and its current value} - **Cut when**: {the observation under which this change is deleted} ## What {1-3 sentence description of what this change does and why} ## Context | File | Role | |------|------| | `src/components/Navbar.tsx` | Will be modified — add logout button | | `src/hooks/useAuth.ts` | Context — provides logout function | | `src/components/Navbar.test.tsx` | Will be modified — add test for logout | ## Requirements 1. {Requirement 1 — clear, testable} 2. {Requirement 2} 3. {Requirement 3} ## Plan 1. {Step 1 — what to change and where} 2. {Step 2} 3. {Step 3} ## Tasks - [ ] {Task 1} - [ ] {Task 2} - [ ] {Task 3} - [ ] {Test task} ## Done When - [ ] All tasks checked off - [ ] Tests pass - [ ] No lint errorsReport:
# TinySpec Created | Field | Value | |-------|-------| | **File** | `specs/tiny/{feature-name}.md` | | **Tasks** | {N} tasks | | **Files affected** | {N} files | ## Next Steps - Review the tinyspec at `specs/tiny/{feature-name}.md` - Run `/speckit.tinyspec.implement` to build it - Or implement manually — the spec is your checklist
Rules
- One file only — never generate separate spec.md, plan.md, tasks.md for tinyspec
- Keep it short — the entire tinyspec should be under 80 lines
- No boilerplate — skip sections that add no value for this specific task
- Concrete file references — always list the actual files that will be changed
- Testable requirements — every requirement must be verifiable
- Warn on scope creep — if the task grows beyond 5 files or 10 tasks, recommend upgrading to full SDD
- Respect constitution — follow project conventions from
.specify/memory/constitution.md
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.

