tranquocthong
UserSpec-driven dev for Claude Code — a messy SRS (or just an idea) → a reviewed Solution Design → traceable, adaptive implementation. Keyless, no lock-in.
Categories
Indexed Skills (3)
commit
spec-flow SHIP step: conventional-commit + push + surface the merge/pull-request link, VCS-agnostic (GitHub + GitLab), with a base-branch guard. Branch creation is owned by the lifecycle commands (/sf:ingest, /sf:bug, /sf:change) via the engine's branch-ensure; this skill commits on the current work branch and refuses to commit on the configured base branch. Invoke ONLY in spec-flow context — explicitly as /sf:commit, or from the /sf:phase ship step. Do NOT auto-trigger on a bare "commit"/"commit push" request — that is the user's own commit workflow, not this skill.
manual-test
Guide for manual testing backend services locally via curl OR Kafka event triggers, with direct DB/Redis verification. Polymorphic by stack: java-spring (Summer Framework X-Userinfo + Keycloak ROPC, plain Spring JWT), node, python, go, dotnet. Use this skill when: testing APIs locally, creating auth tokens, seeding test data, verifying callback webhooks, producing Kafka events to trigger consumers, or debugging API responses. Also trigger when user says: "manual test", "test locally", "curl test", "seed data", "produce event", or wants to verify a fix.
srs-to-sd
Convert an approved SRS into a Solution Design and drive the hybrid spec-flow. Use this skill when the user mentions an SRS, a Solution Design (SD), "convert SRS to SD", starting a feature from a spec, re-syncing after Product changed the SRS, or running a fix/enhance loop on an implemented feature. Routes to the right spec-flow command.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.