nvzver/claude-marketplace
20 skills
$npx skills add nvzver/claude-marketplaceSkillInstalls
actor-templateUse when authoring or editing an actor — a Skill, slash command, or workflow that prescribes how to act (not just what is true).checkCheck roadmap hygiene and apply approved fixes. Input: none. Output: proposed row diffs (stale/inconsistent entries — missing pitch, status vs branch mismatch,…decomposeDecompose a pitch into independently-shippable epics. Input: a pitch slug or path (argument; if omitted, the highest-priority backlog pick).delegatediscoverExtract user intent and gather the codebase facts a spec will rest on. Output — intent + cited facts, handed to specify.doctorRun when the user asks for a health check of their NVZver marketplace install — "doctor", "health check", "verify install", "is my install wired", "something's…flow-selectorApply before any non-trivial task — when the work touches behavior, adds a new module, changes an API or data model, exceeds ~5 files, or lacks an existing…ground-rulesApply on every substantive task — answering questions, drafting, research, analysis, planning, coding, reviewing — whenever the response contains any factual…implementPlan and run parallel implementation of roadmap epics — the parallel build-execution entry point.initInitialize the LSA spec tree on a project. Output — spec tree + module specs.nextRecommend what to work on next. Input: none (or a plain 'what's next' / 'recommend an order' question).observeStart a live observe-and-coach session that rides Claude Code's self-paced /loop and reacts to your file changes through a chosen role.outputApply to every human-facing output — agent responses, skill bodies, plan files, READMEs, commit messages, PR descriptions, comments.reconcileVerify the implementer's diff against the spec (after delegation) — does it work, only what's needed, and all of the plan — then absorb drift.reuse-firstApply on any coding task before writing code — implement a feature, fix a bug, refactor, add code, write a function, wire up a component.revise-constitutionPromote a finished feature's lessons into permanent rules. Output — updated constitution + standards.shapeShape a new feature from a vague idea into a structured pitch. Input: problem or opportunity description (argument or interactive prompt).specifyWrite the grounded spec — EARS requirements, user flows, and Gherkin acceptance scenarios. Output — requirements.md + <flow>.feature files.verifyGround the spec against the codebase BEFORE delegating. Output — GROUNDED / NOT-GROUNDED + grounding.md.verify-checkpointGrade ONE signalled increment as a gate — in either of two invocation modes with identical grading: per-increment dispatch (how lsa:delegate drives it) or a…