starwave-smolspec_skill

Overview

This skill creates a compact, executable specification for small code changes that do not warrant the full spec workflow. It combines automated research, scope assessment, a proposed feature name, and lightweight documentation (smolspec and tasks) so engineers can implement and verify minor changes quickly. The skill enforces escalation rules and quality checks to avoid under-scoping complex work.

How this skill works

The skill first inspects the codebase to estimate complexity (LOC, file count, affected components) and looks for existing specs or related work. If the change fits micro-plan criteria, it generates a sanitized kebab-case feature name and waits for user approval. Then it produces two concise documents: specs/{feature_name}/smolspec.md and specs/{feature_name}/tasks.md, plus an optional decision_log.md when decisions are recorded.

When to use it

• Fixing or adding a small feature expected under ~80 lines of code
• Making a single-component change touching 1–3 files
• Implementing a clear requirement that follows existing code patterns
• Creating verifiable, developer-focused tasks for a minor change
• When you need a minimal, self-contained spec for an AI or engineer to execute

Best practices

• Run the skill only for isolated changes; escalate if multiple subsystems are affected
• Provide a concise prompt and the preferred feature name when available
• Approve or adjust the proposed feature name before proceeding
• Review the generated smolspec.md for assumptions and clarify ambiguous requirements
• Ensure tasks remain outcome-focused and include verification steps

Example use cases

• Add a missing validation for a single form field following existing validation patterns
• Introduce a toggle flag and implement small conditional logic in one module
• Refactor a helper function used by a single component without wider API changes
• Fix a rendering bug confined to a single view file
• Add a small unit test and fixture for an isolated utility function