Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →avizmarlon/new-project
Project bootstrap standard — guarantees all 25 core engineering and product disciplines are consulted in lifecycle order.
Passed 12 of 21 test cases with the skill, and 5 of 21 without it.
and 6 more in the full report
9 fixed4 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
During active build work, what skill identifier enforces PR workflows and prohibits direct local merges into the main branch?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes git-pr-rules to enforce pull request merging | Missed | Passed |
The instructions your model reads when the skill loads.
This skill aggregates 25 core disciplines — engineering, product, testing, documentation, and security — into a single executable checklist. It exists because auto-triggering of individual skills is unreliable, and demanding that every new build apply the complete standard requires explicit invocation, not passive hopes.
Invoking new-project once = a guarantee that all mandatory skills below are consulted at the right moment in the project lifecycle.
invoke column. Mark its todo completed once consulted.completed with a one-line note "N/A — " rather
than deleting it. The point is a conscious decision, never a silent skip.Do not batch all 25 Skill invocations into one turn — that floods context with end-of-session guidance while you're still planning. Pull each one in as its phase arrives.
| Skill | invoke | why here |
|---|---|---|
| Brainstorming | superpowers:brainstorming | Explore intent/requirements/user intent BEFORE any build. Process skill — runs first. |
| Project context | (optional: load project OWNER.md / README if exists) | If project has existing vision/stack docs, read them. Else skip. |
| Search-first ✦ | (rule, not a skill) | Verify external facts (tool behavior, API limits, versioning, third-party state) before asserting them. Embedded behavior for the whole session. |
| Skill | invoke | why here |
|---|---|---|
| Agent Flywheel | agent-flywheel | Plan-space-first: cost of fixing error in plan (~1x) vs. in code (~25x). Picks the build mode. |
| Plan synthesis | superpowers:writing-plans | Multi-phase execution plan with checkpoints, or single-phase sprint plan. |
| Red-team the plan | superpowers:requesting-code-review or manual adversarial pass | Challenge assumptions, identify failure modes, stress-test requirements. |
| Impact metrics | impact-metrics-gate | Define primary success metric + measurement + baseline BEFORE building. |
| Business validation ⟳ | business-guardrails | Validate before building: market fit, competitive gap, anti scope-creep. Only when product/business angle exists. |
test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.