All authors
Claude Skills by ymatrix1
github.com/ymatrix112 skills0 installs0 views
- Phase PlanTurn a Vantage ROADMAP phase into an epic bean with child beans, dependencies and acceptance criteria. Use when starting work on a phase.Votes: 0GitHub stars: 12
- Research TaskRun a Vantage research bean (APIs, formats, measurements, tool comparisons) and record findings in docs/research/. Use for any bean tagged research.Votes: 0GitHub stars: 12
- Start TaskStandard procedure to start any task in Vantage. Finds or creates the bean, creates a branch or worktree, writes the structured plan, and checks the relevant docs.Votes: 0GitHub stars: 12
- Update SpecKeep Vantage docs (PRD, ROADMAP, ARCHITECTURE, UX, specs, DECISIONS, OPEN-QUESTIONS) in sync with a design or code change. Use when changing behaviour, interfaces or decisions, or when editing docs.Votes: 0GitHub stars: 12
- Answer ReviewWork through pull request review comments one by one - verify each finding against the code, fix it with proof, and reply only after the lines actually changed. Use when the user asks to address, fix, answer or resolve review comments, bot findings or requested changes on a PR.Votes: 0GitHub stars: 12
- Close The LoopFind the people waiting on you or on your work, and draft the message for each - a reply you owe, a nudge when you're waiting on someone, or a "shipped" note to whoever asked for the work. Never sends; the user sends. Use when the user asks "who's waiting on me?", "who do I owe a reply?", "draft a follow-up", "tell them it shipped", or after work is merged or deployed.Votes: 0GitHub stars: 12
- Explain Top DownExplain a complex topic, status, decision or design top-down for a busy reader - headline first, then Situation-Complication-Resolution, a MECE breakdown, one concrete example and a visual. Use when the user asks to explain, summarize, compare, or "help me understand" something non-trivial, or when an answer would otherwise be long.Votes: 0GitHub stars: 12
- HandoffWrite or read a short handoff note so work survives /compact, /clear, closed terminals and the next day. Use when ending a session, before compacting, when switching to another task, or when starting a session and asking "where was I?", "what's the state?", "resume", or "continue".Votes: 0GitHub stars: 12
- Land The DayEnd-of-day ritual that closes open loops so work doesn't follow you home - find uncommitted work, unproven edits, open questions and promises, and decide for each one whether to close, park or schedule it, then write handoff notes. Use when the user says "land the day", "wrap up", "end of day", "I'm stopping", or "what's still open?".Votes: 0GitHub stars: 12
- Plan TaskTurn a request into a short, structured task plan before starting work - Context, Higher Goal, Acceptance Criteria, Out of Scope, Summary of Changes - and use the same structure for the PR description at the end. Use when starting any non-trivial task, when the user asks to "plan", "scope" or "break down" work, or when opening a pull request.Votes: 0GitHub stars: 12
- Prove ItProve a change works before calling it done - run a check that exercises the changed code after the last edit, show the command and result, and state its proof level. Use before saying "done", "fixed", "works" or "optimized", and whenever asked to verify, test or confirm a change.Votes: 0GitHub stars: 12
- Record DecisionRecord a decision with its Context, Decision, Why, Alternatives and Impact, plus who decided and its status, in the project's decision log. Use when a choice between options is made (by the user or by you), when the user says "decide", "let's go with", "record this", or when you made a non-obvious choice the user didn't ask for.Votes: 0GitHub stars: 12