{
  "markdown": "# document-driven-development\n\nA standalone, reusable skill repository for document-driven development planning workflows.\n\nThis repository packages a canonical skill family that helps move work through a staged planning flow:\n\n- `ddd-workflow`\n- `ddd-competitive-analysis`\n- `ddd-spec`\n- `ddd-design`\n- `ddd-roadmap`\n- `ddd-version`\n- `ddd-task`\n- `ddd-execute`\n- `ddd-sync`\n\n## Workflow\n\nOptional first stage:\n\n- `ddd-competitive-analysis -> ddd-spec` when the user wants competitor references before spec work\n\nMain flow:\n\n- `ddd-spec -> ddd-design -> ddd-roadmap -> ddd-version -> ddd-task -> ddd-execute`\n\nSupporting follow-up:\n\n- `ddd-sync` updates related planning artifacts after execution progress or completion\n\n## Repository model\n\nThis repository uses a canonical-source-plus-adapters structure.\n\n- Canonical agent guidance: `AGENTS.md`\n- Runtime compatibility symlinks: `CLAUDE.md`, `GEMINI.md`, `CODEX.md`, `OPENCODE.md`, `OPENCLAW.md`\n- Canonical authored source: `skills/`\n- Platform metadata: `.claude-plugin/`, `.codex-plugin/`, `gemini-extension.json`\n- Runtime adapter notes: `adapters/`\n\nThe root guidance file is `AGENTS.md`. Runtime-specific filenames such as `CLAUDE.md`, `GEMINI.md`, `CODEX.md`, `OPENCODE.md`, and `OPENCLAW.md` are compatibility symlinks that point to the same canonical instructions.\n\nThe canonical skill text stays host-agnostic. Runtime-specific installation and packaging guidance lives in adapter docs.\n\n## Compatibility\n\nThis repository is organized to support:\n\n- Claude Code\n- Codex\n- Gemini\n- OpenCode\n- OpenClaw\n- other runtimes that can consume local skill or prompt directories\n\nCompatibility here means the repository provides a stable canonical source and adapter surface. It does not assume identical discovery rules across runtimes, so adapter-specific install details should be documented per runtime rather than embedded into the shared skill text.\n\n## Claude Code usage\n\nClaude-facing metadata lives at:\n\n- `.claude-plugin/plugin.json`\n\nCodex metadata lives at:\n\n- `.codex-plugin/plugin.json`\n\nGemini extension metadata lives at:\n\n- `gemini-extension.json`\n\n## Usage prompts\n\nExample prompts for testing the skill family:\n\n- Use `ddd-workflow` for this feature idea.\n- Use `ddd-workflow` for this feature idea and start with `ddd-competitive-analysis` against Claude Code and Codex.\n- I have competitor references for this feature. Should we do `ddd-competitive-analysis` before `ddd-spec`?\n- Draft the `ddd-competitive-analysis` report for this planning topic.\n- Should this change start as `ddd-spec`, or is it ready to go straight into `ddd-design`, `ddd-roadmap`, or `ddd-version` planning?\n- Draft the `ddd-spec` for this idea.\n- The `ddd-spec` is ready. What should the `ddd-design` stage cover before `ddd-roadmap` placement?\n- Does this need technical design, UI design, or both?\n- I need UI design for this feature. I'll provide a mockup link — what should the design doc cover?\n- I need UI design for this feature, but I do not have a mockup yet. What inputs are missing before we finalize UI details?\n- Where on the `ddd-roadmap` does this belong now that `ddd-spec` and `ddd-design` are ready?\n- Which `ddd-version` should own this work?\n- Break this feature into a `ddd-task` checklist.\n- Use `ddd-execute` for this approved task checklist.\n- Implement the next `ddd-task` item in strict TDD mode.\n- We finished the checklist implementation. Should we run `ddd-sync` now?\n- We finished this milestone. What docs should be synced now with `ddd-sync`?\n\nThe canonical skill content lives in `skills/`.\n\n## Structure\n\n```text\n.\n├── AGENTS.md\n├── CLAUDE.md -> AGENTS.md\n├── GEMINI.md -> AGENTS.md\n├── CODEX.md -> AGENTS.md\n├── OPENCODE.md -> AGENTS.md\n├── OPENCLAW.md -> AGENTS.md\n├── README.md\n├── LICENSE\n├── skills/                                      # canonical authored source\n├── .claude-plugin/\n│   └── plugin.json\n├── .codex-plugin/\n│   └── plugin.json\n├── gemini-extension.json\n└── adapters/                                    # runtime-specific notes and packaging guidance\n```\n\nThe repository keeps only one canonical authored source at `skills/`.\nThere is no longer any repo-local `.claude/` compatibility layer in the repository itself.\n\nClaude compatibility now comes from the root guidance files plus `.claude-plugin/` metadata.\n\n## Adapters\n\n`adapters/` is where runtime-specific installation notes should live. Keep verified runtime differences there instead of splitting the canonical skill text by host.\n\n## Validation\n\nRun this check from the repository root:\n\n```bash\ntest -d skills/ddd-workflow\n```\n\nThis verifies that the canonical skill source exists.\n",
  "bytes": 4648,
  "sha": "24e3628ef6f76dd1e13b17f9fe99c4b680964ec03152118b6c1e79c004647898",
  "repo_slug": "goweii/document-driven-development",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_goweii_document_driven_development_639b3f79/readme"
}