writing-design-docs

To write design documentation for a new software feature, generate structured docs using a Purpose/Behavior/Verify format. This ensures features and systems are well-documented by detailing their purpose, expected behavior, and verification steps.

Keep technical documentation in sync by enforcing documentation updates within the same pull request as related code modifications. This prevents knowledge silos and ensures docs stay current with evolving architecture.

The Purpose/Behavior/Verify format for architecture documentation is a structured approach that clearly defines a system's purpose, outlines its expected behavior, and details the steps to verify functionality, making systems easier to maintain and scale.

Store feature documentation in the `docs/features/` directory and architecture documentation in the `docs/architecture/` directory. This standardized placement prevents knowledge silos and organizes system documentation effectively.

You do not need any specific dependencies to generate feature documentation. The Skill operates independently to create structured design docs and enforce documentation synchronization within your pull requests.

Create design docs for your codebase when implementing new features or systems to prevent knowledge silos. Generating documentation during the development process ensures systems are easier to understand, maintain, and scale over time.