New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Using Bigpowers

by danielvm-git in danielvm-git/bigpowers

One-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation.

MITAuto-check passedDevelopment

Install Using Bigpowers

skills CLI
$ npx skills add danielvm-git/bigpowers --skill using-bigpowers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install danielvm-git/bigpowers using-bigpowers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/using-bigpowers .claude/skills/using-bigpowers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
using-bigpowers
GitHub stars
256
Token cost
~1.3k tokens
SKILL.md length
414 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

One-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation.

  • Works in 3 steps: Read profiles/solo-git.md. → Register with compose-workflow →… → Ship with release-branch in solo-local…
  • Starting with bigpowers for the first time
  • SKILL.md covers Install, What bigpowers is, The lifecycle at a glance and Where to start, plus 4 more sections
  • Calls gh, npx and npm

What it does

Using Bigpowers is an agent skill from danielvm-git/bigpowers. One-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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Git. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.

When your agent uses it

  • Starting with bigpowers for the first time
  • User asks where do I start?
  • The skills system needs to be explained

Example prompts

  • “where do I start?”
  • “/using-bigpowers”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read profiles/solo-git.md.
  2. Register with compose-workflow → specs/WORKFLOW-solo-git.md.
  3. Ship with release-branch in solo-local mode (land-branch.sh), not gh pr create.

What it can do on your machine

Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • npx
    • npm
    • git
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • npmjs.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Using Bigpowers loads about 1.3k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 414 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 414 words, ~1,274 tokens.

Download SKILL.mdSave it as .claude/skills/using-bigpowers/SKILL.md (or your agent's skills folder).
name
using-bigpowers
description
One-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.
model
sonnet
effort
standard

Using bigpowers

HARD GATE — HARD GATE — This skill is the entry point. Do NOT skip it when onboarding new users or starting a new session. It establishes the bigpowers methodology, lifecycle phases, and conventions.

Welcome to bigpowers — a lifecycle of agent skills for production-ready, TDD-driven software by solo developers. The live catalog and its count are generated in SKILL-INDEX.md; never hardcode the number here.

Install

bash
npx bigpowers setup           # one-shot setup
npm install -g bigpowers       # global install
bigpowers setup                # sync skills + link to your tools

From source: git clone → bash scripts/install.sh. Package: bigpowers on npm.

Reach tools: Cline — native AGENTS.md reader (no extension). Aider — opt-in .aider.conf.yml with read: AGENTS.md (Aider-AI/aider). Codex CLI — optional .codex/config.toml via seed-conventions; global ~/.codex/AGENTS.md from install.sh.

What bigpowers is

A curated set of skills organized around the PMBOK developer lifecycle. Each skill does one thing. Skills reference each other by name only — low coupling, high cohesion. All written output goes to specs/ at your project root.

The lifecycle at a glance

See orchestrate-project for the canonical 6-phase lifecycle.

BOOTSTRAP   using-bigpowers (this skill, first time only)
              ↓
DISCOVER    survey-context → research-first → elaborate-spec
              ↓
DESIGN      model-domain / define-language / grill-me / deepen-architecture / design-interface
              ↓
PLAN        scope-work → slice-tasks → plan-work / plan-refactor
              ↓
INITIATE    kickoff-branch → guard-git / hook-commits / seed-conventions
              ↓
SPIKE?      spike-prototype → (feeds back to plan-work)
              ↓
EXECUTE     develop-tdd + enforce-first ←→ delegate-task / dispatch-agents / execute-plan
              ↓
VERIFY      run-evals → verify-work
              ↓
HARDEN      wire-observability (any phase)
              ↓
BUG?        investigate-bug → diagnose-root → validate-fix
              ↓
REVIEW      audit-code → request-review → respond-review
              ↓
INTEGRATE   commit-message → release-branch
              ↓
SUSTAIN     inspect-quality / organize-workspace (ongoing)

UTILITY     terse-mode / craft-skill / edit-document (any phase)

Where to start

Your situationFirst skill to call
Greenfield project, nothing set upseed-conventions
Existing project, new tasksurvey-context
Vague idea that needs shapingelaborate-spec
Plan exists, ready to implementkickoff-branch → develop-tdd
Bug to fixinvestigate-bug
Code ready for reviewaudit-code
Shipping a featurecommit-message → release-branch
Solo dev, PRs feel heavyEnable profiles/solo-git.md → specs/WORKFLOW-solo-git.md → land via scripts/land-branch.sh

Solo Git profile

If you work alone and do not want PR ceremony every task:

  1. Read profiles/solo-git.md.
  2. Register with compose-workflow → specs/WORKFLOW-solo-git.md.
  3. Ship with release-branch in solo-local mode (land-branch.sh), not gh pr create.

You still use worktrees, protected main, and verification gates — only the integrate step changes.

Show full SKILL.md (157 more words)Show less

YAML cockpit and dashboard

Operational source of truth:

  • specs/state.yaml — session, active epic/story, handoff
  • specs/release-plan.yaml — release index and epic list
  • specs/epics/eNN-*.yaml — stories and tasks with verify
  • specs/execution-status.yaml — done/pending per story

Start the HTTP dashboard with visual-dashboard → GET /api/status?projectDir=<abs> and GET /cockpit.html for a read-only PM view.

Key conventions

  • specs/ is your memory. All domain docs, plans, and investigation outputs go in specs/ at your project root.
  • Integrate: team default is gh pr (team-pr); solo profile uses land-branch.sh. Never create GitHub issues from skills — use local Markdown files instead.
  • One skill, one thing. If you're unsure which skill to call, call survey-context — it reads your current state and recommends the next step.
  • verify: every step. Every epic task must have verify: <runnable command>. Evidence over claims.
  • The full catalog is auto-generated. See SKILL-INDEX.md; find skills with search-skills.

After this

Call survey-context to read your project's current state and get a personalized recommendation for where to go next.

<!-- story: e03s02 -->

© danielvm-git, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/using-bigpowers of danielvm-git/bigpowers.

Open the folder on GitHubat commit 812d57a

Compare with similar skills

Using Bigpowers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Using Bigpowers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Using Bigpowers this skilldanielvm-git/bigpowers256—~1.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything85k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    85k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    85k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from danielvm-git/bigpowers

All 39 skills in this repo

  • Extract Design

    danielvm-git/bigpowers

    Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose.

    256 GitHub stars~1k tokensUpdated 16 days ago
    Auto-check passed

  • Align Grid

    danielvm-git/bigpowers

    Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one.

    256 GitHub stars~3k tokensUpdated 16 days ago
    Auto-check passed

  • Assess Impact

    danielvm-git/bigpowers

    Analyze the blast radius of a proposed change before any code is written.

    256 GitHub stars~766 tokensUpdated 16 days ago
    Auto-check passed

  • Audit Code

    danielvm-git/bigpowers

    Self-review checklist for the coding agent to run before dispatching a reviewer.

    256 GitHub stars~1.6k tokensUpdated 16 days ago
    Auto-check: notes

  • Audit Plan

    danielvm-git/bigpowers

    Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins.

    256 GitHub stars~880 tokensUpdated 16 days ago
    Auto-check passed

  • Compose Workflow

    danielvm-git/bigpowers

    Chain multiple bigpowers skills into a custom workflow recipe saved in specs/.

    256 GitHub stars~723 tokensUpdated 16 days ago
    Auto-check passed

Works with

Categories

Questions about Using Bigpowers

What does Using Bigpowers do?

One-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation. Using Bigpowers is an agent skill from danielvm-git/bigpowers. One-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation.

When should I use Using Bigpowers?

Using Bigpowers fits situations like: starting with bigpowers for the first time; user asks where do I start?; the skills system needs to be explained.

How do I install Using Bigpowers in Claude Code?

Run `npx skills add danielvm-git/bigpowers --skill using-bigpowers -a claude-code`. Or copy the skill folder (skills/using-bigpowers in danielvm-git/bigpowers) into .claude/skills/using-bigpowers in your project. Claude Code loads it when a task matches its description.

How do I install Using Bigpowers in Codex?

Run `npx skills add danielvm-git/bigpowers --skill using-bigpowers -a codex`. Or copy the skill folder (skills/using-bigpowers in danielvm-git/bigpowers) into .agents/skills/using-bigpowers in your project. Codex loads it when a task matches its description.

Can I use Using Bigpowers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill using-bigpowers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-bigpowers, .gemini/skills/using-bigpowers, .github/skills/using-bigpowers and .opencode/skills/using-bigpowers in your project.

What does Using Bigpowers need to run?

Going by SKILL.md and its folder, Using Bigpowers needs the command-line tools its instructions call (gh, npx, npm, git and bash). Our summary lists: Node.js.

Does Using Bigpowers access the network?

SKILL.md names 2 domains. As links in the text: npmjs.com and github.com. This is read from the text; nothing was executed.

Is Using Bigpowers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Using Bigpowers use?

Using Bigpowers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Using Bigpowers use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Using Bigpowers?

Skills that share tags, products or a category with Using Bigpowers: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Using Bigpowers?

danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.

Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.