Cursor rule

1---
2description: "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."
3alwaysApply: false
4---
5 
6# Using bigpowers
7> **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.
8 
9 
10Welcome 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`](../../SKILL-INDEX.md); never hardcode the number here.
11 
12## Install
13 
14```bash
15npx bigpowers setup           # one-shot setup
16npm install -g bigpowers       # global install
17bigpowers setup                # sync skills + link to your tools
18```
19 
20From source: `git clone` → `bash scripts/install.sh`. Package: [bigpowers on npm](https://www.npmjs.com/package/bigpowers).
21 
22**Reach tools:** **Cline** — native AGENTS.md reader (no extension). **Aider** — opt-in `.aider.conf.yml` with `read: AGENTS.md` ([Aider-AI/aider](https://github.com/Aider-AI/aider)). **Codex CLI** — optional `.codex/config.toml` via seed-conventions; global `~/.codex/AGENTS.md` from install.sh.
23 
24## What bigpowers is
25 
26A 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.
27 
28## The lifecycle at a glance
29 
30See orchestrate-project for the canonical 6-phase lifecycle.
31 
32```
33BOOTSTRAP   using-bigpowers (this skill, first time only)
34              ↓
35DISCOVER    survey-context → research-first → elaborate-spec
36              ↓
37DESIGN      model-domain / define-language / grill-me / deepen-architecture / design-interface
38              ↓
39PLAN        scope-work → slice-tasks → plan-work / plan-refactor
40              ↓
41INITIATE    kickoff-branch → guard-git / hook-commits / seed-conventions
42              ↓
43SPIKE?      spike-prototype → (feeds back to plan-work)
44              ↓
45EXECUTE     develop-tdd + enforce-first ←→ delegate-task / dispatch-agents / execute-plan
46              ↓
47VERIFY      run-evals → verify-work
48              ↓
49HARDEN      wire-observability (any phase)
50              ↓
51BUG?        investigate-bug → diagnose-root → validate-fix
52              ↓
53REVIEW      audit-code → request-review → respond-review
54              ↓
55INTEGRATE   commit-message → release-branch
56              ↓
57SUSTAIN     inspect-quality / organize-workspace (ongoing)
58 
59UTILITY     terse-mode / craft-skill / edit-document (any phase)
60```
61 
62## Where to start
63 
64| Your situation | First skill to call |
65|---------------|---------------------|
66| Greenfield project, nothing set up | `seed-conventions` |
67| Existing project, new task | `survey-context` |
68| Vague idea that needs shaping | `elaborate-spec` |
69| Plan exists, ready to implement | `kickoff-branch` → `develop-tdd` |
70| Bug to fix | `investigate-bug` |
71| Code ready for review | `audit-code` |
72| Shipping a feature | `commit-message` → `release-branch` |
73| Solo dev, PRs feel heavy | Enable `profiles/solo-git.md` → `specs/WORKFLOW-solo-git.md` → land via `scripts/land-branch.sh` |
74 
75## Solo Git profile
76 
77If you work alone and do not want PR ceremony every task:
78 
791. Read [profiles/solo-git.md](../../profiles/solo-git.md).
802. Register with `compose-workflow` → `specs/WORKFLOW-solo-git.md`.
813. Ship with `release-branch` in **solo-local** mode (`land-branch.sh`), not `gh pr create`.
82 
83You still use worktrees, protected `main`, and verification gates — only the integrate step changes.
84 
85## YAML cockpit and dashboard
86 
87Operational source of truth:
88 
89- `specs/state.yaml` — session, active epic/story, handoff
90- `specs/release-plan.yaml` — release index and epic list
91- `specs/epics/eNN-*.yaml` — stories and tasks with `verify`
92- `specs/execution-status.yaml` — done/pending per story
93 
94Start the HTTP dashboard with `visual-dashboard` → `GET /api/status?projectDir=<abs>` and `GET /cockpit.html` for a read-only PM view.
95 
96## Key conventions
97 
98- **specs/ is your memory.** All domain docs, plans, and investigation outputs go in `specs/` at your project root.
99- **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.
100- **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.
101- **verify: every step.** Every epic task must have `verify: <runnable command>`. Evidence over claims.
102- **The full catalog is auto-generated.** See `SKILL-INDEX.md`; find skills with `search-skills`.
103 
104## After this
105 
106Call `survey-context` to read your project's current state and get a personalized recommendation for where to go next.
107 
108 
109 
110<!-- story: e03s02 -->
111