πŸͺ¦
AutomationShell

Define Success

by danielvm-git

Define Success is an Automation skill for Claude Code, published by danielvm-git in bigpowers.

173 stars14 forkson danielvm-git/bigpowersAdded 2026/09/07+8% in starsRepository updated 2026/09/06
ai-agentsautomationbmadclaude-codeclean-codecursor-rulesdevopsdocumentation-as-codegemini-cliproductivitysoftware-engineeringsolo-developerspec-driven-developmenttdd
Install in seconds
Install Define Success
Copy Define Success into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/danielvm-git/bigpowers/tree/main/skills/define-success ~/.claude/skills/define-success

Requires Node.js. Downloads this skill only β€” not the rest of the repository β€” into your Claude Code skills folder.

Without Node.js

git clone https://github.com/danielvm-git/bigpowers.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/define-success/SKILL.md in danielvm-git/bigpowers
Installs to
~/.claude/skills/define-success
Collection
One of 23 skills cataloged from this repository
Category
Automation β€” 2109 skills

What Define Success does

Define Success is a tombstoned stub that redirects users to plan-work after a rename or merge. Use it only during the transition period before the stub is removed.

Define Success is cataloged under Automation on DirSkills. Define Success comes from a repository tagged ai-agents, automation, bmad, claude-code and clean-code.

Documentation

README

define-success (tombstoned)

This skill has been renamed or merged into plan-work. Use plan-work instead.

This stub exists for one release as a transition aid, then is removed once scripts/validate-tombstones.sh flags it as expired.

Frequently asked about Define Success

  • What else does danielvm-git publish alongside Define Success?

    Define Success is one of 23 skills that DirSkills catalogs from danielvm-git/bigpowers, the repository it ships in. Its siblings there include Align Grid, Assess Impact and Audit Code. Each one is a separate skill with its own page in this directory, installs the same way Define Success does, and is maintained by danielvm-git in that same repository. The rest of the collection is listed on the danielvm-git/bigpowers page.

  • How does Define Success compare to other Automation skills?

    Define Success ranks #1966 by stars among the 2109 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Define Success against them. Open each page to compare what they document and how they install.

More from danielvm-git/bigpowers

Define Success is one of 23 skills cataloged on DirSkills from danielvm-git/bigpowers.

See all 23 skills β†’
πŸ“
2h ago

Align Grid

Align Grid builds MΓΌller-Brockmann modular grid webpages with CSS-variable-driven columns, baseline rhythm, and optical alignment. Use it when you need a visible, load-bearing grid that can be toggled and verified with a Puppeteer harness.
Frontend
17314
πŸ”
2h ago

Assess Impact

Assess Impact analyzes the blast radius of a proposed change before code is written. It maps dependents, affected stories, and test coverage, then writes specs/IMPACT_LATEST.md.
Quality
17314
βœ…
2h ago

Audit Code

Audit Code runs a self-review checklist before requesting review or committing. It checks security, tests, types, conventions, and code quality, then produces pass/fail results.
Quality
17314
🧭
2h ago

Audit Plan

Audit Plan evaluates an incoming project plan against bigpowers principles and conventions, then records gaps and a READY or NOT READY verdict before build work starts. Use it when a new project arrives or before seeding conventions in an unfamiliar codebase.
AI Engineering
17314
πŸ—οΈ
2h ago

Build Epic

Build Epic orchestrates a nine-step build cycle for one epic, from threat modeling and planning through TDD, verification, audit, commit, and release. Use it to resume or run release work with state tracked in YAML files.
DevOps
17314
πŸ—‚οΈ
2h ago

Change Request

Change Request adds or reorders release requirements against specs/release-plan.yaml and epic capsules. Use it when a new requirement arrives mid-release or the plan needs reprioritization.
DevOps
17314