develop-small-feature

# Develop Small Feature Implement the feature or fix described below, carrying it through the full branch → TDD → static checks → user verification → commit → PR lifecycle. This skill is scoped to small, well-scoped changes (a handful of files, a settled approach). For large or uncertain work — spanning many files, needing real debugging/trial-and-error, or warranting a deep review — use `heavy-implementer` and/or the `code-review`/`simplify` skills directly instead of forcing this flow. Spec: $ARGUMENTS If no spec is given as an argument, use the specification already established in this conversation (the user's most recent instructions, requirements already discussed, or an agreed-on OpenSpec change). Do not ask the user to repeat themselves if the spec is already clear from context; ask only if it is genuinely ambiguous. ## Steps 1. **Feature branch.** Run `git branch --show-current`. - If already on a branch other than the repository's default branch (e.g. an existing `feature/*` branch), stay on it — do not switch. - If on the default branch, invoke the **create-feature-branch** skill to create and switch to a new feature branch derived from the spec. 2. **Implement, test-first.** Invoke the **tdd** skill to implement the change (red → green → refactor), delegating the work to the **implementer** agent by default. Do not use `heavy-implementer` unless the user explicitly asks for it, or `implementer` reports (or a retry shows) that the ...