Windsurf rules

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