documentation

To generate an Architecture Decision Record (ADR), use this Skill to draft the document explaining your decision-making process while adhering to corporate technical writing standards. It automatically structures the ADR within your project's `docs/` directory to ensure discoverability and proper linking.

The best way to prevent orphan knowledge is by applying context engineering principles to organize files within a structured `docs/` directory. This approach ensures all README files and runbooks are well-linked, discoverable, and consistently formatted for developers and AI agents.

Yes, you can create runbooks and README files using github-flavored-markdown, standard markdown, or mdx formats. The Skill generates and manages this technical documentation while enforcing corporate writing standards and context engineering guidelines.

Context engineering requires placing technical documentation within a structured `docs/` directory to maintain discoverability. This setup ensures that generated ADRs, runbooks, and README files are properly linked rather than isolated, preventing orphan knowledge across the project.

To update a project README for a new authentication module, use this Skill to draft the changes alongside generating a corresponding runbook and ADR. It structures the updates within the `docs/` directory to maintain clear, consistent technical writing standards.

You need to create an Architecture Decision Record (ADR) when you must document the decision-making process behind a specific architectural choice, rather than using a README file which explains how to use the project. The Skill drafts both formats using context engineering to keep them linked.