القائمة
Use when enforcing plans, verifying requirements, or linking to GitHub. Trigger with planning ops request. Loaded by ai-maestro-architect-agent-main-agent
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | amaa-planning-patterns-ops |
| description | Use when enforcing plans, verifying requirements, or linking to GitHub. Trigger with planning ops request. Loaded by ai-maestro-architect-agent-main-agent |
| context | fork |
| user-invocable | false |
| agent | ai-maestro-architect-agent-main-agent |
Operational procedures for enforcing, validating, and linking planning outputs. Covers enforcement mechanisms, scripts, TDD integration, requirement immutability, plan verification, and GitHub issue linking.
Copy this checklist and track your progress:
| Document | Content |
|---|---|
| enforcement-mechanisms.md | Overview of Enforcement, Plan Validation Script (validate_plan.py), Shared Thresholds Module (thresholds.py), Handoff Protocols, Integration Workflow |
| scripts-reference.md | Universal Analysis Scripts, Core Planning Scripts, Template Generation Scripts, Analysis Scripts, Task Tracker Scripts |
| tdd-planning.md | TDD Planning Principles, TDD Phase Planning, TDD Task Template Extension, TDD Verification Checklist, Integration with Planning Phases |
| requirement-immutability.md | Planning Phase Requirement Check, Plan Structure Requirements, Forbidden Planning Actions, Correct Planning Approach |
| plan-verification-guide.md | Overview, Part 1: Verification Patterns, Part 2: Checklist Template & Task Tracker Integration, Part 3: Examples, Best Practices, Troubleshooting, Related Documentation |
| plan-file-linking.md | Purpose, Linking Requirements, Overview, Implementation Plan, Sub-Plans, Plan File Naming Convention, Automatic Linking |
Example: "Validate plan and link to GH-42" triggers enforcement checks and GitHub linking.
| Issue | Fix |
|---|---|
| Validation failing | Run validate_plan.py --verbose |
| Missing plan links | Check plan-file-linking requirements |
| TDD steps skipped | Review tdd-planning checklist |
| Type | Description |
|---|---|
| Validation report | Plan quality assessment |
| Linked plans | Plans connected to GitHub issues |
See Reference Documents table above.
Use when decomposing systems into modules with clear boundaries. Trigger with modularization or module boundary request. Loaded by ai-maestro-architect-agent-main-agent
Use when designing architectures, identifying risks, creating roadmaps, or breaking work into tasks. Trigger with planning or architecture design request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing requirements, initializing plans, or approving transitions. Trigger with requirements analysis or plan initialization request. Loaded by ai-maestro-architect-agent-main-agent
Use when recording stack choices, constraints, or managing handoffs. Trigger with session memory ops request. Loaded by ai-maestro-architect-agent-main-agent
Use when persisting decisions, patterns, and constraints across sessions. Trigger with session memory or handoff request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing design document states or lifecycle transitions. Trigger with design lifecycle or state transition request. Loaded by ai-maestro-architect-agent-main-agent
