deepwork_rules.define

You can enforce file-change governance rules during AI coding sessions by defining deterministic triggers that activate automated checks, documentation sync, and code review prompts when specific files are modified.

Automating documentation sync when project files change is achieved by creating structured rules that capture file-change triggers and actionable instructions, ensuring related docs are consistently updated without manual intervention.

Setting up code review triggers for specific file modifications involves capturing trigger patterns and safety conditions in a rule file, which then automatically prompts the required review actions across your software project.

Yes, you can stack multiple file-change rules to extend automated workflows across a project, allowing governance rules to be composed and triggered together for comprehensive coverage of documentation and code review processes.

The generated file-change rule uses a YAML frontmatter format saved under the .deepwork/rules/ directory, providing a clear, testable structure for deterministic automation triggers and actions.

No dependencies are required to define deterministic file-change rules, as the skill guides you through an interactive workflow to capture triggers, safety conditions, and actions before generating the rule file.