メニュー
Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs/ directory.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.
Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn "I want X" into a concrete spec.
Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose plan-work change, edit skill via craft-skill, re-run benchmark, record ADR. Use when a skill underperforms on benchmark or stocktake finds systemic gap.
Interactive assumption-surfacing Q&A that stress-tests a plan through relentless questioning until every decision is resolved. Use when user wants to challenge a plan, validate decisions from conversation/context, or mentions "grill me". For doc-grounded variant, use grill-with-docs.
Block dangerous git commands (push, force push, reset --hard, clean, branch -D, checkout/restore .) and enforce Conventional Commits & Branch Protection before an AI agent runs them. Installs hook scripts for Claude Code, Cursor, Cursor CLI, and Gemini CLI; documents Google Antigravity Terminal deny lists. Use when the user wants git safety hooks, to block git push or destructive git in agents, or to mirror the same policy across AI coding tools.
| name | write-document |
| model | sonnet |
| description | Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs/ directory. |
| disable-model-invocation | true |
Create high-signal technical documentation that serves as an expert collaborator for both humans and AI. This skill enforces the BMAD principles to prevent context rot and ensure architectural durability.
Distinct from edit-document: Use this skill to create a document that does not yet exist. Use edit-document when a document already exists and needs restructuring, clarity, or prose improvements.
HARD GATE — Every document must have a clear "Reason for Existence." If a document doesn't provide actionable leverage for a caller or test, do not create it.
| Principle | Execution |
|---|---|
| Bold | Make strong assertions. Define clear boundaries and "Never" rules. No "it might" or "usually." |
| Minimal | High-density, low-filler. Circuit Breaker: If the file exceeds 300 lines or the session exceeds 20 turns, you MUST run terse-mode and compact state before saving. |
| Actionable | Link every doc to a verifiable outcome. Architectural Docs: Verify via Gherkin features (specs/verifications/features/) or grep-based structure checks (grep -c "pattern" file) that prove the design's constraints are present. |
| Durable | Design for the long-term. Scalability: Use "Nested Indexing"—root files link to module-level GEMINI.md indexes; do not list individual sub-files in the root. |
Choose the correct BMAD-BigPowers artifact:
specs/adr/).specs/tech-architecture/tech-stack.md).<module>/REFERENCE.md).specs/verifications/features/).README.md at project root).Cross-Cutting Concerns: If a doc affects multiple modules, place the authoritative source in the lowest common ancestor directory and use "Delegates" (one-line pointers) in sub-directories to maintain the Single Source of Truth without violating the Stepdown Rule.
STREAM CONTINUITY — When writing file content, output in continuous chunks of ~200 lines. Do not pause. Continue immediately until complete. If you need time, emit a placeholder comment rather than going silent.
Write the document focusing on "Expert Collaboration":
README.md at project root using the template in REFERENCE.md — no TOC, no second interview round.CLAUDE.md commands if available; use TODO markers otherwise.edit-document for polish.→ verify: grep -c "^## " README.md | awk '{if($1>=7) print "OK"}'
Before finalizing, audit the document against these red flags:
README.md), not specs/.GEMINI.md is updated. If the module's index is new, add it to the root GEMINI.md.scripts/sync-skills.sh if the document is a SKILL.md or affects generated artifacts.verify: command. For architecture, this can be a grep or run_shell_command that validates the existence of required files or patterns.elaborate-spec.Suggest next skill: audit-code or sync-skills.sh.
Combined from dbader/readme-template and jehna/readme-best-practices. No TOC.
| Lines | Section |
|---|---|
| 1 | Title |
| 5–16 | Navigation |
| 18–24 | Sections intro |
| 26–178 | README section templates (1–15) |
| 180–183 | Verify |
# Project Name
Fill badges from CLAUDE.md stack info if available. Default to license + version badges.
> One-line description of what this project does and why it matters.
2-3 paragraphs: what problem it solves, who it's for, and what makes it different.
## Prerequisites
- **Runtime**: Node.js v18+ (from CLAUDE.md)
- **Package manager**: npm (or pnpm/yarn)
Auto-fill from CLAUDE.md commands section when possible.
## Installation
```bash
npm install -g your-package
# or
npx your-package
Prefer npx one-shot if applicable; list global install as alternative.
### 6. Usage
```markdown
## Usage
```bash
your-command --help
your-command do-something
Include the most common 1-2 commands. Link to full docs if they exist.
### 7. Features
```markdown
## Features
- Feature 1: short description
- Feature 2: short description
3-6 bullet points of what the project does. Derived from the project's purpose.
## Configuration
| Variable | Default | Description |
|----------|---------|-------------|
| `VAR_NAME` | `value` | What it controls |
Use TODO markers if unknown.
## Development
```bash
git clone <repo-url>
cd project
npm install
Auto-fill from CLAUDE.md `Run` and `Build` commands.
### 10. Running Tests
```markdown
## Tests
```bash
npm test
npm run lint
Auto-fill from CLAUDE.md `Test` and `Lint` commands.
### 11. Contributing
```markdown
## Contributing
1. Fork the repo.
2. Create a feature branch (`git checkout -b feature/my-thing`).
3. Commit changes (`git commit -am 'Add my thing'`).
4. Push (`git push origin feature/my-thing`).
5. Open a Pull Request.
## Changelog
See [CHANGELOG.md](../../CHANGELOG.md) or [Releases](https://github.com/user/repo/releases).
## Links
- Repository: https://github.com/user/repo
- Issue tracker: https://github.com/user/repo/issues
## License
MIT — see [LICENSE](../../LICENSE) for details.
Detect from CLAUDE.md or project LICENSE file.
## Credits
Built with [bigpowers](https://github.com/danielvm-git/bigpowers).
After generation, run: grep -c "^## " README.md — expect ≥ 7 section headings.