dev-playbook — bundle index
Bundle OKF 0.1 · 10 conceitos · GeoffNordling/dev-playbook
Open source Repository Open in the app JSON README (API)
About
# dev-playbook — bundle index
The meta repo that governs every other repository in the workspace: what they
standardize on, how their work is tracked and built, and how the agents that
work them are configured. Start at [dev-playbook](/README.md).
- [dev-playbook](/README.md) — The dev-playbook meta repo — workspace standards, the software factory definition, agent configuration, CLI tools, and reusable harness patterns
- [Candidates](/CANDIDATES.md) — Uncommitted future work — described, not yet promoted to issues
- [Vocabulary](/CONTEXT.md) — The workspace's established vocabulary — the canonical terms to use exactly
## Directories
- [doc-types/](/doc-types/index.md) — The documentation type system — what a doc-type is, this repo's instantiation, and one directory per built doc-type
- [docs/](/docs/index.md) — Surveys of third-party tooling and the Decision Records
- [dotfiles/](/dotfiles/index.md) — Claude Code configuration — skills, rules, settings, hooks — managed via GNU Sto
Details
- Kind
- OKF bundles
- Topic
- Files & documents
- Publisher
- geoffnordling
- Origin
- okf_github
- Category
- dados
- Version
- 0.1
- Stars
- 1
- Last push
- 2026-09-08T23:57:43Z
- Repository state
- ativo
- Language
- Python
- Added
- 2026-09-08 22:11:44
- Updated
- 2026-09-08 22:11:44
- Origin id
GeoffNordling/dev-playbook:index.md
README
--- type: README title: dev-playbook description: The dev-playbook meta repo — workspace standards, the software factory definition, agent configuration, CLI tools, and reusable harness patterns --- # dev-playbook Standards and tools for djinn wrangling across a multi-repo workspace. > *"Often, when we find a recurring problem, something that happens over and over again, we pull the team together, ask them to try harder, do better – essentially, we ask for good intentions. This rarely works… When you are asking for good intentions, you are not asking for a change… because people already had good intentions. But if good intentions don't work, what does? Mechanisms work."* > — Amazon leadership principles > > *"…to succeed in executing spontaneous and unconscious technique, it is necessary to train in it in a highly conscious fashion."* > — Miyamoto Musashi > > *"A little bit of slope makes up for a lot of intercept."* > — John Osterhaus, Stanford Lecture ## What belongs here - Cross-project standards and conventions - Formal standards governing the workspace - Agent configuration (skills, rules, settings) - CLI tools and shared libraries for workspace automation ## What does NOT belong here - Project-specific documentation — put it in that project's repo - Application code ## The workspace All repos live under a single root directory: `~/workspace/`. One meta repo governs everything else: **dev-playbook** (this repo). ## What's here The top-level directories are listed in [`index.md`](/index.md). > **`dotfiles/`** — after adding or removing files, run `scripts/sync-dotfiles` from the main checkout only; it relinks live `$HOME`, so it's a user step, never run from a per-issue worktree.