Skip to content

Claude Skills by danielvm-git

github.com/danielvm-git

296 skillsA× 285B× 8C× 30 installs67 views

Plan ReleaseARELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. NOT a planning-spine substitute: it does not scope work (scope-work) or write story tasks (plan-work). Use after elaborate-spec when the user wants a versioned release index of epics.developmentbashsecurityVotes: 0GitHub stars: 274
Plan TestsADesign a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles.developmentrailsVotes: 0GitHub stars: 274
Plan WorkAPLANNING SPINE STEP 3 of 3 — Plan the work: write detailed implementation tasks into the active epic capsule (specs/epics/eNN-slug/). Produces countable-story-format .md specs and runnable -tasks.yaml files. Use after slice-tasks (step 2). Not a substitute for scope-work (step 1) or slice-tasks (step 2).developmentgobashVotes: 0GitHub stars: 274
Publish PackageAPackage registry publishing for npm, crates.io, PyPI, and Homebrew. Verifies prerequisites, runs the publish command, confirms success, and surfaces actionable error hints on failure.developmentgoVotes: 0GitHub stars: 274
Quick FixAStreamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.developmentgobashVotes: 0GitHub stars: 274
Release BranchAMake the merge/PR/keep/discard decision for a feature branch, verify coverage gates, create the PR with gh, and clean up the worktree. Use when a feature is done and ready to ship, or when user says "release", "merge", or "open a PR".developmentbashgitVotes: 0GitHub stars: 274
Skills DirectorySkills Directory 3 slots · $399/mo · one ad per page · sponsors can never buy grades.See placements
Request ReviewADispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.developmentgobashVotes: 0GitHub stars: 274
Research FirstALook-before-build — search registries, repo, existing skills, and web for prior art before implementing. Appends Prior Art to the spec. Use after survey-context and before elaborate-spec, when adding dependencies, or when the task may already be solved.developmentbashapiVotes: 0GitHub stars: 274
Reset BaselineARestore the project to a known clean state between agent runs or experiments. Use between benchmark runs, after a failed spike, or when user wants a clean working tree.developmentgogitVotes: 0GitHub stars: 274
Respond ReviewAAct on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.developmentgobashVotes: 0GitHub stars: 274
Run BenchmarkARun skill quality benchmarks from specs/benchmarks/ definitions — N-run with/without-skill delta grading, train/validation split, pass@k + benchmark.json reports. Use before and after evolve-skill to prove quality changes are improvements, not regressions.developmentgobashVotes: 0GitHub stars: 274
Run EvalsAEval-Driven Development — define capability and regression evals before building; code graders use verify commands, model graders use explicit rubrics; log pass@k. Use before develop-tdd on new features, or when measuring agent capability over runs.developmentshellVotes: 0GitHub stars: 274
Run PlanningADISCOVER-PHASE ADVANCER — Drive the discover-phase checklist (specs/planning-status.yaml) through survey-context → scope-work → research-first → elaborate-spec → plan-release → slice-tasks. NOT a duplicate of plan-work or the planning spine; it orchestrates the pre-coding discover phase only.developmentpythongoVotes: 0GitHub stars: 274
Scope WorkAPLANNING SPINE STEP 1 of 3 — Scope the work: define what is in and out of scope and save as specs/product/SCOPE_LATEST.yaml. Use before slice-tasks or plan-release on any new initiative. Not a substitute for slice-tasks (step 2) or plan-work (step 3).developmentgobashVotes: 0GitHub stars: 274
Search SkillsAFind the right bigpowers skill from natural-language intent using a local lexical index over SKILL.md frontmatter. Use when unsure which skill to invoke, or at start of research-first.developmentbashapiVotes: 0GitHub stars: 274
Security ReviewAAI-powered security analysis of code changes — traces data flow, detects injection, auth bypass, secrets exposure, and unsafe deserialization across files. Use when reviewing pending changes, before release-branch, during verify-work Phase 5, during build-epic Step 0 threat modeling, or when the user says "security review" or "scan for vulns".developmentrustgoVotes: 0GitHub stars: 274
Seed ConventionsAGenerate CLAUDE.md and CONVENTIONS.md for a brand-new project through a brief interview, and create the specs/ directory with evolved bigpowers structure (product/, tech-architecture/, verifications/, epics/archive/). Entry point for greenfield projects. Use when starting a new project from scratch, when user asks to set up AI agent conventions, or when there is no CLAUDE.md yet.developmenttypescriptgoVotes: 0GitHub stars: 274
Session StateATrack implementation decisions and progress in specs/state.yaml to prevent context rot. Use at the start of a session to load context, and whenever a significant decision is made or a milestone is reached.developmentgobashVotes: 0GitHub stars: 274
Setup EnvironmentAPre-install dependencies and configure tools before development work begins. Use at session start on a fresh clone, before kickoff-branch, or when user says setup environment or install deps.developmentswiftbashVotes: 0GitHub stars: 274
Simple EnglishAWrite or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so the result is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the 53 rules of the standard (Issue 9...developmentpythonapiVotes: 0GitHub stars: 274
Simulate AgentsARun Mock User and Auditor agents against a feature in fresh contexts before human review. Use after verify-work, before request-review, when user wants pre-review simulation.developmenttestingsecurityVotes: 0GitHub stars: 274
Slice TasksAPLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.developmentbashapiVotes: 0GitHub stars: 274
Smoke TestAPost-deploy health-check against a live URL. Validates HTTP status, response content, and critical endpoints. Runnable standalone OR as the final step of the deploy skill.developmentbashVotes: 0GitHub stars: 274
Spike PrototypeAThrow-away prototype for unknown problem spaces. Output is learning notes in specs/archive/spikes/SPIKE-<name>.md, not production code. Use when the domain or technology is unexplored, when estimates are impossible without experimentation, or when user says "spike", "prototype", or "proof of concept".developmentapiVotes: 0GitHub stars: 274
Stocktake SkillsASequential subagent batch audit of the bigpowers skill catalog — Quick Scan (changed only) or Full (all skills). Use during sustain phase, before a major release, or when catalog drift is suspected.developmentgobashVotes: 0GitHub stars: 274
Survey ContextAPer-task context bootstrap — reads existing specs/ and tech-architecture docs to map the current lifecycle phase and suggest the next skill. Use at the start of any task, when returning after a break, or when unsure what to do next. For deriving a tech-stack doc from scratch, use map-codebase first.developmentgobashVotes: 0GitHub stars: 274
Terse ModeAFallback ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use ONLY when context is critically long and compressing output is necessary to continue. Not a strategy — token discipline comes from code shape (small functions, unique names, headless tests), not terser prompts. Use when user says "caveman mode", "terse mode", "less tokens", "be brief", or invokes /terse-mode.developmentsqlsecurityVotes: 0GitHub stars: 274
Trace RequirementALink story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Produces specs/TRACEABILITY_LATEST.md. Use when you want to verify coverage of a release plan, audit which stories are implemented, or find "dark" stories with no code.developmentnodeVotes: 0GitHub stars: 274
Using BigpowersAOne-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation. Use when starting with bigpowers for the first time, when user asks "where do I start?", or when the skills system needs to be explained.developmentgobashVotes: 0GitHub stars: 274
Validate ContractsAAssert data shape consistency across system boundaries — live API responses against JSON Schema, key-set comparison across layers, data shape validation for migrations and exports. Catches silent data corruption before deploy.developmentbashapiVotes: 0GitHub stars: 274
Validate FixAProve a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says "is this fixed?", or before closing an investigation.developmentshellbashVotes: 0GitHub stars: 274
Verify WorkAMulti-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-by-step manual verification, gaps-closure loop. Use after execute-plan or develop-tdd, before audit-code.developmentgoshellVotes: 0GitHub stars: 274
Visual DashboardAStart a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.developmentbashgitVotes: 0GitHub stars: 274
Wire CiACI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.developmentpythonrustVotes: 0GitHub stars: 274
Wire ObservabilityAAdd structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.developmentbashsqlVotes: 0GitHub stars: 274
Write DocumentAWrite, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs/ directory.developmentgoshellVotes: 0GitHub stars: 274
E23 Benchmark InfrastructureACreate `run-benchmark/SKILL.md` — the skill that reads benchmark definitions from `specs/benchmarks/`, executes each scenario's grader, and outputs a structured pass@k report that `evolve-skill` can consume.developmentbashgitVotes: 0GitHub stars: 274
E26 Security ReviewA**BCPs:** 5 **Status:** tododevelopmentrustgoVotes: 0GitHub stars: 274
E31 Quality GuaranteeASTORY KEY: E31-S07 TITLE: Wire golden suite into evolve-skill regression checks TYPE: Story PARENT: e31 STATUS: Draft AUTHOR: dvm DATE: 2026-07-02 MATURITY: 3 SIZE: XS evolve-skill currently uses run-benchmark for capability evaluations (measuring whether a skill improved). It lacks a fast regression check — if a skill edit breaks the sync pipeline or compliance, evolve-skill won't catch it until CI runs. Wiring run-golden-suite.sh as a pre-benchmark regressi...developmentgosecurityVotes: 0GitHub stars: 274
E38 Traceability GateASTORY KEY: E38-S06 TITLE: Create gate-trace skill — deterministic quality gate before release TYPE: Story PARENT: e38 STATUS: Draft AUTHOR: dvm DATE: 2026-07-03 MATURITY: 3 SIZE: S The traceability pipeline now has a coverage matrix (e38s01) and blind-spot detector (e38s04), but there is no single gate that combines them into a release-blocking decision. The gate-trace skill reads both artifacts, applies deterministic decision rules (TEA-inspired PASS/CONCERN...developmentVotes: 0GitHub stars: 274
E39 Knowledge GraphASTORY KEY: E39-S07 TITLE: Create maintain-wiki skill — agent-maintained OKF ingest, lint, and query TYPE: Story PARENT: e39 STATUS: Draft AUTHOR: dvm DATE: 2026-07-03 MATURITY: 3 SIZE: M The OKF bundles (skills-wiki, conventions-wiki, agent-guide) are generated but not maintained. As the codebase evolves — new skills, changed conventions, updated CLAUDE.md — the wikis stale. The maintain-wiki skill gives agents the ability to maintain the knowledge graph: ING...developmentVotes: 0GitHub stars: 274
E79 Agentic SteA**Epic:** e79 | **Story:** e79s02 | **Status:** done | **BCPs:** 3developmentgobashVotes: 0GitHub stars: 274
craft-skillA**Type:** Skill **Model:** sonnet **Effort:** standard Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle. --- *Auto-generated by scripts/build-skill-graph.sh*developmentVotes: 0GitHub stars: 274
evolve-skillA**Type:** Skill **Model:** opus **Effort:** standard Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose plan-work change, edit skill via craft-skill, re-run benchmark, record ADR. Use when a skill underperforms on benchmark or stocktake finds systemic gap. --- *Auto-generated by scripts/build-skill-graph.sh*developmentVotes: 0GitHub stars: 274
Negative PathAThis skill does not have any HARD GATE callout blocks, which violates the superpowers compliance requirement.developmentgoVotes: 0GitHub stars: 274
Skill Verify Fail OpenANegative-path fixture for run-skill-verify.sh — must never PASS.developmentVotes: 0GitHub stars: 274