|
| 1 | +version: "1.0" |
| 2 | +base_url: "https://github.com/PaulDuvall/ai-development-patterns?tab=readme-ov-file" |
| 3 | +patterns: |
| 4 | + # Foundation (6 patterns) |
| 5 | + - id: readiness-assessment |
| 6 | + name: Readiness Assessment |
| 7 | + category: foundation |
| 8 | + maturity: beginner |
| 9 | + anchor: "#readiness-assessment" |
| 10 | + automatable: false |
| 11 | + description: > |
| 12 | + Systematic evaluation of codebase and team readiness for AI integration. |
| 13 | + related: [codified-rules, issue-generation] |
| 14 | + |
| 15 | + - id: codified-rules |
| 16 | + name: Codified Rules |
| 17 | + category: foundation |
| 18 | + maturity: beginner |
| 19 | + anchor: "#codified-rules" |
| 20 | + automatable: true |
| 21 | + description: > |
| 22 | + Version and maintain AI coding standards as explicit configuration files. |
| 23 | + related: [readiness-assessment, security-sandbox, context-persistence, progressive-disclosure, event-automation, guided-refactoring] |
| 24 | + |
| 25 | + - id: security-sandbox |
| 26 | + name: Security Sandbox |
| 27 | + category: foundation |
| 28 | + maturity: beginner |
| 29 | + anchor: "#security-sandbox" |
| 30 | + automatable: true |
| 31 | + description: > |
| 32 | + Run AI tools in isolated environments without access to secrets or sensitive data. |
| 33 | + related: [codified-rules, security-orchestration, policy-generation, event-automation] |
| 34 | + |
| 35 | + - id: developer-lifecycle |
| 36 | + name: Developer Lifecycle |
| 37 | + category: foundation |
| 38 | + maturity: intermediate |
| 39 | + anchor: "#developer-lifecycle" |
| 40 | + automatable: false |
| 41 | + description: > |
| 42 | + Structured 9-stage process from problem definition through deployment with AI assistance. |
| 43 | + related: [codified-rules, security-sandbox, spec-driven-development, observable-development, automated-traceability, tool-integration] |
| 44 | + |
| 45 | + - id: tool-integration |
| 46 | + name: Tool Integration |
| 47 | + category: foundation |
| 48 | + maturity: intermediate |
| 49 | + anchor: "#tool-integration" |
| 50 | + automatable: true |
| 51 | + description: > |
| 52 | + Connect AI systems to external data sources, APIs, and tools for enhanced capabilities beyond prompt-only interactions. |
| 53 | + related: [security-sandbox, developer-lifecycle] |
| 54 | + |
| 55 | + - id: issue-generation |
| 56 | + name: Issue Generation |
| 57 | + category: foundation |
| 58 | + maturity: intermediate |
| 59 | + anchor: "#issue-generation" |
| 60 | + automatable: true |
| 61 | + description: > |
| 62 | + Generate Kanban-optimized work items from requirements using AI to ensure continuous flow with clear acceptance criteria and dependencies. |
| 63 | + related: [readiness-assessment] |
| 64 | + |
| 65 | + # Development (17 patterns) |
| 66 | + - id: spec-driven-development |
| 67 | + name: Spec-Driven Development |
| 68 | + category: development |
| 69 | + maturity: intermediate |
| 70 | + anchor: "#spec-driven-development" |
| 71 | + automatable: true |
| 72 | + description: > |
| 73 | + Use executable specifications to guide AI code generation with clear acceptance criteria before implementation. |
| 74 | + related: [developer-lifecycle, custom-commands, image-spec, atomic-decomposition] |
| 75 | + |
| 76 | + - id: planned-implementation |
| 77 | + name: Planned Implementation |
| 78 | + category: development |
| 79 | + maturity: beginner |
| 80 | + anchor: "#planned-implementation" |
| 81 | + automatable: true |
| 82 | + description: > |
| 83 | + Generate explicit implementation plans before writing code to improve quality, reduce iterations, and enable better collaboration. |
| 84 | + related: [progressive-enhancement] |
| 85 | + |
| 86 | + - id: progressive-enhancement |
| 87 | + name: Progressive Enhancement |
| 88 | + category: development |
| 89 | + maturity: beginner |
| 90 | + anchor: "#progressive-enhancement" |
| 91 | + automatable: true |
| 92 | + description: > |
| 93 | + Build complex features through small, deployable iterations rather than big-bang generation. |
| 94 | + related: [planned-implementation, atomic-decomposition, image-spec, choice-generation] |
| 95 | + |
| 96 | + - id: context-persistence |
| 97 | + name: Context Persistence |
| 98 | + category: development |
| 99 | + maturity: intermediate |
| 100 | + anchor: "#context-persistence" |
| 101 | + automatable: true |
| 102 | + description: > |
| 103 | + Manage AI context as a finite resource through structured memory schemas, prompt pattern capture, and session continuity protocols. |
| 104 | + related: [codified-rules, progressive-disclosure] |
| 105 | + |
| 106 | + - id: event-automation |
| 107 | + name: Event Automation |
| 108 | + category: development |
| 109 | + maturity: intermediate |
| 110 | + anchor: "#event-automation" |
| 111 | + automatable: true |
| 112 | + description: > |
| 113 | + Execute custom commands automatically at assistant lifecycle events to enforce policies and automate workflows. |
| 114 | + related: [codified-rules, security-sandbox, custom-commands] |
| 115 | + |
| 116 | + - id: custom-commands |
| 117 | + name: Custom Commands |
| 118 | + category: development |
| 119 | + maturity: intermediate |
| 120 | + anchor: "#custom-commands" |
| 121 | + automatable: true |
| 122 | + description: > |
| 123 | + Discover and use built-in command vocabularies, then extend them with custom commands that encode domain expertise and sophisticated workflows. |
| 124 | + related: [event-automation, spec-driven-development, codified-rules] |
| 125 | + |
| 126 | + - id: progressive-disclosure |
| 127 | + name: Progressive Disclosure |
| 128 | + category: development |
| 129 | + maturity: intermediate |
| 130 | + anchor: "#progressive-disclosure" |
| 131 | + automatable: true |
| 132 | + description: > |
| 133 | + Load AI assistant rules incrementally based on task context to prevent instruction saturation and context bloat. |
| 134 | + related: [codified-rules, context-persistence, centralized-rules] |
| 135 | + |
| 136 | + - id: constrained-generation |
| 137 | + name: Constrained Generation |
| 138 | + category: development |
| 139 | + maturity: beginner |
| 140 | + anchor: "#constrained-generation" |
| 141 | + automatable: true |
| 142 | + description: > |
| 143 | + Give AI specific constraints to prevent over-engineering and ensure focused solutions. |
| 144 | + related: [] |
| 145 | + |
| 146 | + - id: atomic-decomposition |
| 147 | + name: Atomic Decomposition |
| 148 | + category: development |
| 149 | + maturity: intermediate |
| 150 | + anchor: "#atomic-decomposition" |
| 151 | + automatable: true |
| 152 | + description: > |
| 153 | + Break complex features into atomic, independently implementable tasks for parallel AI agent execution. |
| 154 | + related: [progressive-enhancement, parallel-agents] |
| 155 | + |
| 156 | + - id: automated-traceability |
| 157 | + name: Automated Traceability |
| 158 | + category: development |
| 159 | + maturity: intermediate |
| 160 | + anchor: "#automated-traceability" |
| 161 | + automatable: true |
| 162 | + description: > |
| 163 | + Maintain automated links between requirements, specifications, tests, implementation, and documentation using AI. |
| 164 | + related: [developer-lifecycle] |
| 165 | + |
| 166 | + - id: guided-architecture |
| 167 | + name: Guided Architecture |
| 168 | + category: development |
| 169 | + maturity: intermediate |
| 170 | + anchor: "#guided-architecture" |
| 171 | + automatable: true |
| 172 | + description: > |
| 173 | + Apply architectural frameworks (DDD, Well-Architected, 12-Factor) using AI to ensure sound system design. |
| 174 | + related: [developer-lifecycle, codified-rules] |
| 175 | + |
| 176 | + - id: guided-refactoring |
| 177 | + name: Guided Refactoring |
| 178 | + category: development |
| 179 | + maturity: intermediate |
| 180 | + anchor: "#guided-refactoring" |
| 181 | + automatable: true |
| 182 | + description: > |
| 183 | + Systematic code improvement using AI to detect and resolve code smells with measurable quality metrics. |
| 184 | + related: [codified-rules] |
| 185 | + |
| 186 | + - id: observable-development |
| 187 | + name: Observable Development |
| 188 | + category: development |
| 189 | + maturity: intermediate |
| 190 | + anchor: "#observable-development" |
| 191 | + automatable: false |
| 192 | + description: > |
| 193 | + Strategic logging and debugging that makes system behavior visible to AI. |
| 194 | + related: [developer-lifecycle] |
| 195 | + |
| 196 | + - id: image-spec |
| 197 | + name: Image Spec |
| 198 | + category: development |
| 199 | + maturity: intermediate |
| 200 | + anchor: "#image-spec" |
| 201 | + automatable: true |
| 202 | + description: > |
| 203 | + Upload images (diagrams, mockups, flows) as primary specifications for AI coding tools to build accurate implementations from visual context. |
| 204 | + related: [spec-driven-development, progressive-enhancement] |
| 205 | + |
| 206 | + - id: choice-generation |
| 207 | + name: Choice Generation |
| 208 | + category: development |
| 209 | + maturity: intermediate |
| 210 | + anchor: "#choice-generation" |
| 211 | + automatable: false |
| 212 | + description: > |
| 213 | + Generate multiple implementation options for exploration and comparison rather than accepting first AI solution. |
| 214 | + related: [progressive-enhancement] |
| 215 | + |
| 216 | + - id: parallel-agents |
| 217 | + name: Parallel Agents |
| 218 | + category: development |
| 219 | + maturity: advanced |
| 220 | + anchor: "#parallel-agents" |
| 221 | + automatable: false |
| 222 | + description: > |
| 223 | + Run multiple AI agents concurrently on isolated tasks or environments to maximize development speed and exploration. |
| 224 | + related: [atomic-decomposition] |
| 225 | + |
| 226 | + - id: error-resolution |
| 227 | + name: Error Resolution |
| 228 | + category: development |
| 229 | + maturity: intermediate |
| 230 | + anchor: "#error-resolution" |
| 231 | + automatable: false |
| 232 | + description: > |
| 233 | + Automatically collect error context from logs, system state, and git history, then use AI to diagnose root causes and generate validated fixes. |
| 234 | + related: [developer-lifecycle, observable-development, tool-integration] |
| 235 | + |
| 236 | + # Operations (4 patterns) |
| 237 | + - id: security-orchestration |
| 238 | + name: Security Orchestration |
| 239 | + category: operations |
| 240 | + maturity: intermediate |
| 241 | + anchor: "#security-orchestration" |
| 242 | + automatable: true |
| 243 | + description: > |
| 244 | + Aggregate multiple security tools and use AI to summarize findings for actionable insights. |
| 245 | + related: [security-sandbox, centralized-rules] |
| 246 | + |
| 247 | + - id: centralized-rules |
| 248 | + name: Centralized Rules |
| 249 | + category: operations |
| 250 | + maturity: advanced |
| 251 | + anchor: "#centralized-rules" |
| 252 | + automatable: true |
| 253 | + description: > |
| 254 | + Enforce organization-wide AI rules through a central Git repository that syncs to standard AI assistant configuration files with automatic language and framework detection. |
| 255 | + related: [codified-rules, progressive-disclosure, security-orchestration] |
| 256 | + |
| 257 | + - id: policy-generation |
| 258 | + name: Policy Generation |
| 259 | + category: operations |
| 260 | + maturity: advanced |
| 261 | + anchor: "#policy-generation" |
| 262 | + automatable: false |
| 263 | + description: > |
| 264 | + Transform compliance requirements into executable Cedar/OPA policy files with AI assistance. |
| 265 | + related: [security-sandbox] |
| 266 | + |
| 267 | + - id: baseline-management |
| 268 | + name: Baseline Management |
| 269 | + category: operations |
| 270 | + maturity: advanced |
| 271 | + anchor: "#baseline-management" |
| 272 | + automatable: false |
| 273 | + description: > |
| 274 | + Establish intelligent performance baselines and configure monitoring thresholds automatically. |
| 275 | + related: [tool-integration] |
0 commit comments