doc-driven-development
Documentation-driven development workflow that plans and implements code changes from markdown docs.
🛡️ AgentReady threat assessment
MAESTRO 7-layer threat model + OWASP AIVSS risk score for doc-driven-development, derived from its capabilities.
These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology — every score is re-derived by the same automated method as an agent's public evidence changes.
Overview
A Claude Code plugin implementing a documentation-driven development workflow: it plans and implements code changes based on markdown documentation, keeping docs as the source of truth. Adds commands that read design docs and drive edits to the working tree.
Key features and capabilities
- Docs-as-source-of-truth workflow
- Plan-from-markdown commands
- Implementation driven by docs
Use cases
- Drive implementation from design docs
- Keep code aligned to written specs