Process Patterns
Patterns and conventions for audit resolution, project planning, and workspace documentation.
Audit and Deviation Resolution
Section titled “Audit and Deviation Resolution”Deviation Resolution as a Formal Process
Section titled “Deviation Resolution as a Formal Process”When an audit identifies deviations from specification, create a formal deviation-resolution.md that:
- Lists each deviation with severity.
- Specifies the exact fix for each.
- References the original specification section.
- Includes verification steps.
This structured approach prevents regressions and ensures complete remediation.
Notification Timing Is the Most Common Audit Deviation
Section titled “Notification Timing Is the Most Common Audit Deviation”Across multiple implementations, the most frequently caught deviation is notifications dispatched inside transactions instead of after commit. Make this a first-pass checklist item during code review.
Project Planning and Task Decomposition
Section titled “Project Planning and Task Decomposition”Prerequisite Tasks Emerge During Planning
Section titled “Prerequisite Tasks Emerge During Planning”When planning notification or lifecycle tasks, always check whether all CRUD operations are implemented first. Prerequisite tasks are frequently discovered only when planning a dependent task.
Update Downstream Plans After Adding Prerequisites
Section titled “Update Downstream Plans After Adding Prerequisites”When a prerequisite task is added to a sequence, update all downstream task plans to assume the prerequisite’s deliverables exist. Review requirements.md, analysis.md, implementation-changes.md, verification.md, and specification.md for each downstream task.
Manager Prompt and Verification Workflows
Section titled “Manager Prompt and Verification Workflows”The /manager-prompt workflow generates project plans, and /verify-project validates implementations. Both should be integrated into the task lifecycle for consistency. Plans generated from /manager-prompt should incorporate the check-api-test-results workflow for verification steps.
Workspace and Documentation Conventions
Section titled “Workspace and Documentation Conventions”Cross-Repository Markdown Links
Section titled “Cross-Repository Markdown Links”Use /<folder>/<path> convention for cross-repository Markdown links. Be aware that a leading / may resolve to the filesystem root instead of the workspace root in some editors and tools.
Grep Before Modifying Core Behaviors
Section titled “Grep Before Modifying Core Behaviors”Changes to validation logic or core service methods can regress unrelated components. Search for all usages before making changes.
Copyright: © Arda Systems 2025-2026, All rights reserved