Guides

Each guide answers one question: how do I do this thing? No theory, no preamble — just the steps and the verification.

• Asking for outcomes — The single most important habit. Anti-pattern → pattern.
• Steering rules — How to teach DOS your preferences once and have them stick.
• Voice notifications — Make DOS announce phase transitions out loud.
• The activity dashboard — Read your work history and live session state.
• File a Feature Request — When you've asked for the same thing three times, file an FR. The DOS team curates Packs.
• Writing a custom Hook — Run code at lifecycle events.
• Writing a custom Skill — Add a new skill to an existing Pack.
• Contributing to DOS — Submit changes, follow the three-copy rule.