speckit-architecture-guard-governed-tasks

To generate architecture-aware task plans, you synthesize constraints from historical decision documents and security artifacts before creating a vetted task list. This prevents implementation drift by validating tasks against existing architecture constitution and trust-boundary requirements.

Governed task orchestration is the process of reading constitution and memory artifacts to validate implementation tasks against historical architecture and security constraints. It ensures generated task lists remain compliant with prior decisions before development begins.

You convert architectural findings into migration tasks by processing security review results and generating module-level corrections. This approach prefers targeted module refactoring over broad rewrites to maintain system stability during implementation.

Yes, you can run security review gates on generated tasks to detect missing validation, authorization, trust-boundary, and audit requirements. The review updates security constraints and captures findings into durable memory after completion.

Yes, generating governed tasks requires explicit file reads of constitution documents and synthesized feature memory or security artifacts. These inputs provide the historical architecture context needed to validate the generated implementation task list.

Use architecture guard workflows for migration planning when your feature requires alignment with prior architectural decisions and security constraints. It grounds tasks in historical context, preventing drift that often occurs with manual task creation in complex systems.