← ClaudeAtlas

speckit-tinyspec-tinyspeclisted

Generate a single lightweight spec file with context, plan, and tasks for small changes
opsmill/infrahub-mcp · ★ 9 · AI & Automation · score 73
Install: claude install-skill opsmill/infrahub-mcp
# 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 ```text $ARGUMENTS ``` You **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 1. Verify a spec-kit project exists by checking for `.specify/` directory 2. Verify git is available and the project is a git repository 3. Verify the user has described the change (if not, ask what they want to build) ## Outline 1. **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.specify` instead - If the task seems too large, warn the user and suggest the full workflow 2. **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 3. **Generate tinyspec