vraj-ai
- 18 skills
- 0 followers
- 14 hours ago last updated
- ▌ Ship · vraj-ai bundleDrive a published spec to verified, pushed completion through a resumable backlog, worktree-isolated parallel builds under a lazy-senior-dev ladder, gate-first review, a milestone reviewer, and a final adversarial teardown. Use when the user invokes /ship, asks to build out a spec autonomously, or resumes a ship run.
- ▌ Goals · vraj-ai bundleDrive a plan document to verified completion through a resumable single-writer backlog, named Worker Role research and review, worktree-isolated parallel builds, milestone gates, and a final adversarial teardown. Use when the user invokes /goal, asks to execute an architecture plan autonomously, resumes a goal, or needs a large issue set delivered milestone by milestone.
- ▌ Audit · vraj-aiAudit a whole codebase rather than a single diff — establish the boundary and baseline, sweep layer by layer (entry points, domain, data, integrations, auth, tests, ops), check every stated invariant for a real enforcement point, a failing-on-violation test, and a production signal, rank findings by blast radius, and emit each as a ticket with a Verification-command. Use when asked to audit an app or codebase, assess a project's health, review before a launch, verify that a security/performance/privacy claim is actually enforced, or produce a prioritized defect backlog.
- ▌ Council · vraj-aiRun independent multi-model research, evidence-based debate, voting, and scoped T0/T1 reviews without rubber-stamping. Use when goals encounters a genuinely contested research item, Phase B needs backlog sanity checks, an item needs independent T0 reviewers, or a milestone needs one rotating integration reviewer.
- ▌ Grill · vraj-aiUser-invoked interview that stress-tests a plan and writes glossary, architecture, and ADRs into CONTEXT/. Use when the user runs /grill.
- ▌ Issues · vraj-aiUser-invoked. Sets up a project's tracker and CONTEXT/ once, then turns a grill into a spec and tracer-bullet tickets. Use when the user runs /issues.
- ▌ Ponytail · vraj-aiForces the laziest solution that actually works; use on coding tasks or when the user says ponytail, be lazy, simplest solution, YAGNI, do less, or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do not use for non-coding requests.
- ▌ Snapshot · vraj-aiUser-invoked session close. Syncs CONTEXT/ and the issue tracker, writes a handoff, then commits and pushes under /snapshot authority. Use when the user runs /snapshot.
- ▌ Pr Review · vraj-ai bundleGitHub Actions PR review bot with Greptile parity — confidence 0-5, risk gates, checks annotations, and fix loop. Install via setup-vskills.
- ▌ Push Handoff · vraj-aiCommit and push a verified handoff plus its artifacts, only under explicit authority, and prove the push happened by reading the remote SHA back. Use as the final delivery step after artifacts are ready, when the user asks to push work, or when a handoff needs to reach the remote. Refuses to claim success without remote proof and never force-pushes or commits secrets.
- ▌ Setup Vskills · vraj-ai bundleSets up this skills repo on a new machine — installs the skills with the vskills CLI, configures pstack model routing for any harness, ensures a verification skill, then regenerates the local-only context docs (CONTEXT.md, docs/) that are deliberately not published in the public repo.
- ▌ Setup Obsidian · vraj-ai bundleTurn a repo's docs folder into a retrieval graph — router, generated indexes, state file — and open it as an Obsidian vault.
- ▌ Council Adversary · vraj-aiTear down a converged item or whole deliverable as a read-only different-model judge, returning falsifiable findings and a blocking verdict. Use for optional hardened T0 review, optional T2 whole-deliverable review, and the mandatory final T3 code-level gate.
- ▌ Implementation Tdd · vraj-aiStrict one-ticket TDD for implementation work — lock the Verification-command before editing, drive red-green at the highest meaningful seam production traffic actually uses, and prove the provider failure modes (duplicate and out-of-order delivery, replay, partial failure, forged payloads, wrong-tenant access) rather than assuming them. Use when implementing a Coding ticket, and whenever the change touches an external provider, a queue, a signed webhook, a billing or provisioning lifecycle, persistence, or auth.
- ▌ Subagent Delegation · vraj-aiFan work out to subagents safely — draw provably disjoint lanes, write the full lane brief, order dependent tickets into waves, and keep the parent as the sole gatekeeper that re-runs every gate and performs every commit and tracker write. Use when parallel or batch work is explicitly authorized, when an authorized ticket range has a dependency graph, when workers share one git checkout, or when any agent or human may be writing the same tree concurrently.
- ▌ Delivery Constraints · vraj-aiDeliver a ticket whose delivery path is decided by something other than the code — a token/spend cap, a live data migration, restricted git authority, an unwritable tracker, or a pipeline state that is lying about progress. Use when budget is capped, when a change touches production data or costs money to run, when push/PR authority is restricted, when tracker writes are unavailable and work must hand off through a file, or when a ticket has been retried with no new evidence and the tracker and the repo disagree.
- ▌ Herdr Orchestrator · vraj-aiInteractive Herdr setup and orchestration for a Grok pane coordinating Codex and three non-OpenCode Council agents.
- ▌ AI Subscription Unit Economics · vraj-aiPricing, limits, and margin gates for a product whose cost of goods is model inference — compute cost per action, cost per active user, and the breakeven limit before choosing a price, then encode the resulting caps as testable invariants. Use when pricing an AI feature or subscription tier, setting rate/usage limits, evaluating whether a plan loses money on heavy users, or estimating the inference cost of a proposed feature.