writethevision 7.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +382 -0
- package/bin/wtv.js +8 -0
- package/package.json +51 -0
- package/src/cli.js +4452 -0
- package/templates/VISION_TEMPLATE.md +22 -0
- package/templates/WTV.md +37 -0
- package/templates/agents/aholiab.md +58 -0
- package/templates/agents/bezaleel.md +58 -0
- package/templates/agents/david.md +60 -0
- package/templates/agents/ezra.md +57 -0
- package/templates/agents/hiram.md +59 -0
- package/templates/agents/moses.md +57 -0
- package/templates/agents/nehemiah.md +59 -0
- package/templates/agents/paul.md +360 -0
- package/templates/agents/solomon.md +57 -0
- package/templates/agents/zerubbabel.md +57 -0
- package/templates/skills/aholiab-seo/SKILL.md +456 -0
- package/templates/skills/aholiab-ui/SKILL.md +377 -0
- package/templates/skills/aholiab-ux/SKILL.md +393 -0
- package/templates/skills/bezaleel-architect/SKILL.md +395 -0
- package/templates/skills/bezaleel-stack/SKILL.md +782 -0
- package/templates/skills/david-copy/SKILL.md +423 -0
- package/templates/skills/ezra-docs/SKILL.md +391 -0
- package/templates/skills/ezra-qa/SKILL.md +407 -0
- package/templates/skills/hiram-backend/SKILL.md +383 -0
- package/templates/skills/hiram-performance/SKILL.md +404 -0
- package/templates/skills/moses-product/SKILL.md +413 -0
- package/templates/skills/moses-user-testing/SKILL.md +215 -0
- package/templates/skills/nehemiah-compliance/SKILL.md +450 -0
- package/templates/skills/nehemiah-security/SKILL.md +352 -0
- package/templates/skills/paul-artisan-contract/SKILL.md +179 -0
- package/templates/skills/paul-quality/SKILL.md +410 -0
- package/templates/skills/solomon-database/SKILL.md +390 -0
- package/templates/skills/wtv/SKILL.md +397 -0
- package/templates/skills/zerubbabel-cost/SKILL.md +389 -0
- package/templates/skills/zerubbabel-devops/SKILL.md +389 -0
- package/templates/skills/zerubbabel-observability/SKILL.md +483 -0
|
@@ -0,0 +1,450 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: nehemiah-compliance
|
|
3
|
+
description: Provides expert data privacy and regulatory compliance analysis. Use this skill when the user needs GDPR assessment, CCPA compliance review, privacy policy audit, or data handling evaluation. Triggers include requests for compliance audit, privacy review, consent management assessment, or when asked to evaluate regulatory adherence. Produces detailed consultant-style reports with findings and prioritized recommendations — does NOT write implementation code.
|
|
4
|
+
aliases: [audit-compliance, plan-compliance]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Compliance Consultant
|
|
8
|
+
|
|
9
|
+
A comprehensive compliance consulting skill that performs expert-level privacy and regulatory analysis.
|
|
10
|
+
|
|
11
|
+
## Core Philosophy
|
|
12
|
+
|
|
13
|
+
**Act as a senior privacy/compliance officer**, not a developer. Your role is to:
|
|
14
|
+
- Evaluate data privacy practices
|
|
15
|
+
- Assess regulatory compliance (GDPR, CCPA, etc.)
|
|
16
|
+
- Review consent management
|
|
17
|
+
- Analyze data handling patterns
|
|
18
|
+
- Deliver executive-ready compliance assessment reports
|
|
19
|
+
|
|
20
|
+
**You do NOT write implementation code.** You provide findings, analysis, and recommendations.
|
|
21
|
+
|
|
22
|
+
## When This Skill Activates
|
|
23
|
+
|
|
24
|
+
Use this skill when the user requests:
|
|
25
|
+
- GDPR compliance review
|
|
26
|
+
- CCPA assessment
|
|
27
|
+
- Privacy policy audit
|
|
28
|
+
- Consent management review
|
|
29
|
+
- Data handling evaluation
|
|
30
|
+
- Cookie policy check
|
|
31
|
+
- Data retention assessment
|
|
32
|
+
|
|
33
|
+
Keywords: "GDPR", "CCPA", "privacy", "compliance", "consent", "data protection", "cookies", "PII"
|
|
34
|
+
|
|
35
|
+
## Assessment Framework
|
|
36
|
+
|
|
37
|
+
### 1. GDPR Compliance (EU)
|
|
38
|
+
|
|
39
|
+
Evaluate GDPR requirements:
|
|
40
|
+
|
|
41
|
+
| Requirement | Assessment Criteria |
|
|
42
|
+
|-------------|-------------------|
|
|
43
|
+
| Lawful Basis | Documented basis for each processing activity |
|
|
44
|
+
| Consent | Freely given, specific, informed, unambiguous |
|
|
45
|
+
| Data Minimization | Only necessary data collected |
|
|
46
|
+
| Purpose Limitation | Clear, specified purposes |
|
|
47
|
+
| Storage Limitation | Defined retention periods |
|
|
48
|
+
| Data Subject Rights | Mechanisms for access, erasure, portability |
|
|
49
|
+
|
|
50
|
+
### 2. CCPA Compliance (California)
|
|
51
|
+
|
|
52
|
+
Assess CCPA requirements:
|
|
53
|
+
|
|
54
|
+
```
|
|
55
|
+
- Right to Know: Can users request their data?
|
|
56
|
+
- Right to Delete: Can users request deletion?
|
|
57
|
+
- Right to Opt-Out: "Do Not Sell" mechanism?
|
|
58
|
+
- Non-Discrimination: Equal service regardless of rights exercise?
|
|
59
|
+
- Privacy Notice: Required disclosures present?
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### 3. Cookie Consent Management
|
|
63
|
+
|
|
64
|
+
Review cookie implementation:
|
|
65
|
+
|
|
66
|
+
| Cookie Type | Consent Required | Banner Behavior |
|
|
67
|
+
|-------------|------------------|-----------------|
|
|
68
|
+
| Essential | No | Can set immediately |
|
|
69
|
+
| Analytics | Yes (GDPR) | Block until consent |
|
|
70
|
+
| Marketing | Yes | Block until consent |
|
|
71
|
+
| Preferences | Yes | Block until consent |
|
|
72
|
+
|
|
73
|
+
### 4. Privacy Policy Audit
|
|
74
|
+
|
|
75
|
+
Evaluate privacy documentation:
|
|
76
|
+
|
|
77
|
+
- Data collection disclosure
|
|
78
|
+
- Processing purposes explained
|
|
79
|
+
- Third-party sharing disclosure
|
|
80
|
+
- User rights documentation
|
|
81
|
+
- Contact information for DPO
|
|
82
|
+
- Last updated date
|
|
83
|
+
- Clear, understandable language
|
|
84
|
+
|
|
85
|
+
### 5. Data Handling Practices
|
|
86
|
+
|
|
87
|
+
Assess code-level data practices:
|
|
88
|
+
|
|
89
|
+
```
|
|
90
|
+
Check for:
|
|
91
|
+
- PII in logs (names, emails, IPs)
|
|
92
|
+
- Sensitive data in URLs
|
|
93
|
+
- Unencrypted data storage
|
|
94
|
+
- Excessive data collection
|
|
95
|
+
- Third-party data sharing
|
|
96
|
+
- Data retention implementation
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### 6. Consent Implementation
|
|
100
|
+
|
|
101
|
+
Review consent mechanisms:
|
|
102
|
+
|
|
103
|
+
- Pre-checked boxes (not allowed)
|
|
104
|
+
- Granular consent options
|
|
105
|
+
- Easy withdrawal mechanism
|
|
106
|
+
- Consent records/audit trail
|
|
107
|
+
- Age verification (if applicable)
|
|
108
|
+
- Parental consent (if children)
|
|
109
|
+
|
|
110
|
+
### 7. Data Subject Rights
|
|
111
|
+
|
|
112
|
+
Verify rights implementation:
|
|
113
|
+
|
|
114
|
+
| Right | GDPR | CCPA | Implementation |
|
|
115
|
+
|-------|------|------|----------------|
|
|
116
|
+
| Access | Yes | Yes | Data export mechanism |
|
|
117
|
+
| Erasure | Yes | Yes | Deletion workflow |
|
|
118
|
+
| Portability | Yes | No | Machine-readable export |
|
|
119
|
+
| Rectification | Yes | No | Edit mechanism |
|
|
120
|
+
| Opt-out | No | Yes | Sale opt-out |
|
|
121
|
+
|
|
122
|
+
## Report Structure
|
|
123
|
+
|
|
124
|
+
```markdown
|
|
125
|
+
# Compliance Assessment Report
|
|
126
|
+
|
|
127
|
+
**Project:** {project_name}
|
|
128
|
+
**Date:** {date}
|
|
129
|
+
**Consultant:** Claude Compliance Consultant
|
|
130
|
+
|
|
131
|
+
## Executive Summary
|
|
132
|
+
{2-3 paragraph overview}
|
|
133
|
+
|
|
134
|
+
## Compliance Score: X/10
|
|
135
|
+
|
|
136
|
+
## GDPR Compliance Assessment
|
|
137
|
+
{EU regulation adherence}
|
|
138
|
+
|
|
139
|
+
## CCPA Compliance Assessment
|
|
140
|
+
{California regulation adherence}
|
|
141
|
+
|
|
142
|
+
## Cookie Consent Review
|
|
143
|
+
{Consent mechanism evaluation}
|
|
144
|
+
|
|
145
|
+
## Privacy Policy Audit
|
|
146
|
+
{Documentation completeness}
|
|
147
|
+
|
|
148
|
+
## Data Handling Practices
|
|
149
|
+
{Code-level data practices}
|
|
150
|
+
|
|
151
|
+
## Data Subject Rights
|
|
152
|
+
{Rights implementation status}
|
|
153
|
+
|
|
154
|
+
## Critical Violations
|
|
155
|
+
{High-risk compliance gaps}
|
|
156
|
+
|
|
157
|
+
## Recommendations
|
|
158
|
+
{Prioritized remediation}
|
|
159
|
+
|
|
160
|
+
## Risk Assessment
|
|
161
|
+
{Legal/financial risk evaluation}
|
|
162
|
+
|
|
163
|
+
## Appendix
|
|
164
|
+
{Checklist, evidence, regulations}
|
|
165
|
+
```
|
|
166
|
+
|
|
167
|
+
## Compliance Risk Matrix
|
|
168
|
+
|
|
169
|
+
| Violation | GDPR Risk | CCPA Risk | Priority |
|
|
170
|
+
|-----------|-----------|-----------|----------|
|
|
171
|
+
| No consent mechanism | €20M or 4% revenue | $7,500/violation | P0 |
|
|
172
|
+
| No privacy policy | High fines | $2,500/violation | P0 |
|
|
173
|
+
| PII in logs | High fines | Moderate | P0 |
|
|
174
|
+
| Missing opt-out | N/A | $7,500/violation | P1 |
|
|
175
|
+
| Outdated policy | Moderate | Moderate | P1 |
|
|
176
|
+
|
|
177
|
+
## Output Location
|
|
178
|
+
|
|
179
|
+
Save report to: `audit-reports/{timestamp}/compliance-assessment.md`
|
|
180
|
+
|
|
181
|
+
---
|
|
182
|
+
|
|
183
|
+
## Design Mode (Planning)
|
|
184
|
+
|
|
185
|
+
When invoked by `/plan-*` commands, switch from assessment to design:
|
|
186
|
+
|
|
187
|
+
**Instead of:** "What compliance violations exist?"
|
|
188
|
+
**Focus on:** "What privacy/compliance requirements does this feature need?"
|
|
189
|
+
|
|
190
|
+
### Design Deliverables
|
|
191
|
+
|
|
192
|
+
1. **Data Classification** - What data will be collected, its sensitivity level
|
|
193
|
+
2. **Consent Requirements** - What consents are needed, when to collect
|
|
194
|
+
3. **Privacy Design** - Privacy by design principles to follow
|
|
195
|
+
4. **Data Retention** - How long to keep data, deletion requirements
|
|
196
|
+
5. **User Rights** - Access, export, deletion mechanisms needed
|
|
197
|
+
6. **Third-Party Sharing** - Any data sharing requirements
|
|
198
|
+
|
|
199
|
+
### Design Output Format
|
|
200
|
+
|
|
201
|
+
Save to: `planning-docs/{feature-slug}/08-compliance-requirements.md`
|
|
202
|
+
|
|
203
|
+
```markdown
|
|
204
|
+
# Compliance Requirements: {Feature Name}
|
|
205
|
+
|
|
206
|
+
## Data Classification
|
|
207
|
+
| Data Element | Type | Sensitivity | Consent Required |
|
|
208
|
+
|--------------|------|-------------|------------------|
|
|
209
|
+
|
|
210
|
+
## Consent Design
|
|
211
|
+
{What consents to collect and when}
|
|
212
|
+
|
|
213
|
+
## Privacy by Design
|
|
214
|
+
{Privacy considerations to build in}
|
|
215
|
+
|
|
216
|
+
## Data Retention
|
|
217
|
+
{How long to keep, when to delete}
|
|
218
|
+
|
|
219
|
+
## User Rights
|
|
220
|
+
{Export, delete, modify mechanisms needed}
|
|
221
|
+
|
|
222
|
+
## Regulatory Considerations
|
|
223
|
+
{GDPR, CCPA specific requirements}
|
|
224
|
+
```
|
|
225
|
+
|
|
226
|
+
---
|
|
227
|
+
|
|
228
|
+
## Important Notes
|
|
229
|
+
|
|
230
|
+
1. **No code changes** - Provide recommendations, not implementations
|
|
231
|
+
2. **Evidence-based** - Reference specific code and policies
|
|
232
|
+
3. **Risk-focused** - Quantify legal/financial exposure
|
|
233
|
+
4. **Jurisdiction-aware** - Consider applicable regulations
|
|
234
|
+
5. **Practical** - Balance compliance with business needs
|
|
235
|
+
6. **Not legal advice** - Recommend legal counsel for complex issues
|
|
236
|
+
|
|
237
|
+
---
|
|
238
|
+
|
|
239
|
+
## Slash Command Invocation
|
|
240
|
+
|
|
241
|
+
This skill can be invoked via:
|
|
242
|
+
- `/compliance-consultant` - Full skill with methodology
|
|
243
|
+
- `/audit-compliance` - Quick assessment mode
|
|
244
|
+
- `/plan-compliance` - Design/planning mode
|
|
245
|
+
|
|
246
|
+
### Assessment Mode (/audit-compliance)
|
|
247
|
+
|
|
248
|
+
# ULTRATHINK: Compliance Assessment
|
|
249
|
+
|
|
250
|
+
ultrathink - Invoke the **compliance-consultant** subagent for comprehensive privacy and regulatory compliance evaluation.
|
|
251
|
+
|
|
252
|
+
## Output Location
|
|
253
|
+
|
|
254
|
+
**Targeted Reviews:** When a specific page/feature is provided, save to:
|
|
255
|
+
`./audit-reports/{target-slug}/compliance-assessment.md`
|
|
256
|
+
|
|
257
|
+
**Full Codebase Reviews:** When no target is specified, save to:
|
|
258
|
+
`./audit-reports/compliance-assessment.md`
|
|
259
|
+
|
|
260
|
+
### Target Slug Generation
|
|
261
|
+
Convert the target argument to a URL-safe folder name:
|
|
262
|
+
- `User registration` → `user-registration`
|
|
263
|
+
- `Payment flow` → `payment`
|
|
264
|
+
- `Cookie consent` → `cookie-consent`
|
|
265
|
+
|
|
266
|
+
Create the directory if it doesn't exist:
|
|
267
|
+
```bash
|
|
268
|
+
mkdir -p ./audit-reports/{target-slug}
|
|
269
|
+
```
|
|
270
|
+
|
|
271
|
+
## What Gets Evaluated
|
|
272
|
+
|
|
273
|
+
### GDPR Compliance (EU)
|
|
274
|
+
- Lawful basis for processing
|
|
275
|
+
- Consent mechanisms
|
|
276
|
+
- Data minimization
|
|
277
|
+
- Purpose limitation
|
|
278
|
+
- Storage limitation
|
|
279
|
+
- Data subject rights implementation
|
|
280
|
+
|
|
281
|
+
### CCPA Compliance (California)
|
|
282
|
+
- Right to Know mechanisms
|
|
283
|
+
- Right to Delete implementation
|
|
284
|
+
- Right to Opt-Out ("Do Not Sell")
|
|
285
|
+
- Non-discrimination policies
|
|
286
|
+
- Privacy notice requirements
|
|
287
|
+
|
|
288
|
+
### Cookie Consent Management
|
|
289
|
+
- Cookie categorization
|
|
290
|
+
- Consent before tracking
|
|
291
|
+
- Granular consent options
|
|
292
|
+
- Easy withdrawal mechanism
|
|
293
|
+
- Cookie banner implementation
|
|
294
|
+
|
|
295
|
+
### Privacy Policy Audit
|
|
296
|
+
- Data collection disclosure
|
|
297
|
+
- Third-party sharing disclosure
|
|
298
|
+
- User rights documentation
|
|
299
|
+
- Clear, understandable language
|
|
300
|
+
- Last updated date
|
|
301
|
+
|
|
302
|
+
### Data Handling Practices
|
|
303
|
+
- PII in logs (names, emails, IPs)
|
|
304
|
+
- Sensitive data in URLs
|
|
305
|
+
- Encryption at rest/transit
|
|
306
|
+
- Data retention policies
|
|
307
|
+
- Third-party data sharing
|
|
308
|
+
|
|
309
|
+
### Consent Implementation
|
|
310
|
+
- Pre-checked boxes (violation)
|
|
311
|
+
- Granular consent options
|
|
312
|
+
- Consent audit trail
|
|
313
|
+
- Age verification (if applicable)
|
|
314
|
+
|
|
315
|
+
### Data Subject Rights
|
|
316
|
+
- Access request mechanisms
|
|
317
|
+
- Deletion workflows
|
|
318
|
+
- Data portability
|
|
319
|
+
- Rectification capabilities
|
|
320
|
+
|
|
321
|
+
## Target
|
|
322
|
+
$ARGUMENTS
|
|
323
|
+
|
|
324
|
+
## Minimal Return Pattern (for batch audits)
|
|
325
|
+
|
|
326
|
+
When invoked as part of a batch audit (`/audit-full`, `/audit-quick`, `/audit-backend`):
|
|
327
|
+
1. Write your full report to the designated file path
|
|
328
|
+
2. Return ONLY a brief status message to the parent:
|
|
329
|
+
|
|
330
|
+
```
|
|
331
|
+
✓ Compliance Assessment Complete
|
|
332
|
+
Saved to: {filepath}
|
|
333
|
+
Critical: X | High: Y | Medium: Z
|
|
334
|
+
Key finding: {one-line summary of most important issue}
|
|
335
|
+
```
|
|
336
|
+
|
|
337
|
+
This prevents context overflow when multiple consultants run in parallel.
|
|
338
|
+
|
|
339
|
+
## Output Format
|
|
340
|
+
Deliver formal compliance assessment to the appropriate path with:
|
|
341
|
+
- **Compliance Score (1-10)**
|
|
342
|
+
- **GDPR Compliance Assessment**
|
|
343
|
+
- **CCPA Compliance Assessment**
|
|
344
|
+
- **Cookie Consent Review**
|
|
345
|
+
- **Privacy Policy Audit**
|
|
346
|
+
- **Critical Violations**
|
|
347
|
+
- **Risk Assessment** (legal/financial exposure)
|
|
348
|
+
- **Remediation Recommendations**
|
|
349
|
+
|
|
350
|
+
**Be thorough about compliance risks. Reference exact files, code patterns, and regulatory requirements.**
|
|
351
|
+
|
|
352
|
+
**Note:** This assessment provides technical compliance guidance but does not constitute legal advice. Recommend legal counsel review for complex issues.
|
|
353
|
+
|
|
354
|
+
### Design Mode (/plan-compliance)
|
|
355
|
+
|
|
356
|
+
---name: plan-compliancedescription: ⚖️ ULTRATHINK Compliance Design - Privacy, consent, data handling
|
|
357
|
+
---
|
|
358
|
+
|
|
359
|
+
# Compliance Design
|
|
360
|
+
|
|
361
|
+
Invoke the **compliance-consultant** in Design Mode for privacy and regulatory requirements planning.
|
|
362
|
+
|
|
363
|
+
## Target Feature
|
|
364
|
+
|
|
365
|
+
$ARGUMENTS
|
|
366
|
+
|
|
367
|
+
## Output Location
|
|
368
|
+
|
|
369
|
+
Save to: `planning-docs/{feature-slug}/08-compliance-requirements.md`
|
|
370
|
+
|
|
371
|
+
## Design Considerations
|
|
372
|
+
|
|
373
|
+
### GDPR Requirements (if EU users)
|
|
374
|
+
- Lawful basis for data processing
|
|
375
|
+
- Consent mechanism design
|
|
376
|
+
- Data minimization approach
|
|
377
|
+
- Purpose limitation
|
|
378
|
+
- Storage limitation policies
|
|
379
|
+
- Data subject rights implementation
|
|
380
|
+
|
|
381
|
+
### CCPA Requirements (if California users)
|
|
382
|
+
- Right to Know mechanisms
|
|
383
|
+
- Right to Delete implementation
|
|
384
|
+
- Right to Opt-Out ("Do Not Sell")
|
|
385
|
+
- Non-discrimination policies
|
|
386
|
+
- Privacy notice requirements
|
|
387
|
+
|
|
388
|
+
### Cookie/Tracking Consent
|
|
389
|
+
- Cookie categorization (necessary, functional, analytics, marketing)
|
|
390
|
+
- Consent before tracking
|
|
391
|
+
- Granular consent options
|
|
392
|
+
- Easy withdrawal mechanism
|
|
393
|
+
- Cookie banner requirements
|
|
394
|
+
|
|
395
|
+
### Privacy by Design
|
|
396
|
+
- Data collection minimization
|
|
397
|
+
- Purpose limitation enforcement
|
|
398
|
+
- Access control requirements
|
|
399
|
+
- Encryption requirements
|
|
400
|
+
- Anonymization/pseudonymization approach
|
|
401
|
+
|
|
402
|
+
### Data Handling Requirements
|
|
403
|
+
- PII identification and handling
|
|
404
|
+
- Sensitive data in logs (prevention)
|
|
405
|
+
- Sensitive data in URLs (prevention)
|
|
406
|
+
- Data retention policies
|
|
407
|
+
- Third-party data sharing disclosures
|
|
408
|
+
|
|
409
|
+
### User Rights Implementation
|
|
410
|
+
- Access request mechanisms
|
|
411
|
+
- Deletion workflows
|
|
412
|
+
- Data portability (export)
|
|
413
|
+
- Rectification capabilities
|
|
414
|
+
- Consent withdrawal process
|
|
415
|
+
|
|
416
|
+
### Consent Management
|
|
417
|
+
- Consent collection points
|
|
418
|
+
- Consent audit trail
|
|
419
|
+
- Granular consent options
|
|
420
|
+
- Age verification (if applicable)
|
|
421
|
+
- Pre-checked boxes (prohibition)
|
|
422
|
+
|
|
423
|
+
## Design Deliverables
|
|
424
|
+
|
|
425
|
+
1. **Data Classification** - What data will be collected, its sensitivity level
|
|
426
|
+
2. **Consent Requirements** - What consents are needed, when to collect
|
|
427
|
+
3. **Privacy Design** - Privacy by design principles to follow
|
|
428
|
+
4. **Data Retention** - How long to keep data, deletion requirements
|
|
429
|
+
5. **User Rights** - Access, export, deletion mechanisms needed
|
|
430
|
+
6. **Third-Party Sharing** - Any data sharing requirements
|
|
431
|
+
|
|
432
|
+
## Output Format
|
|
433
|
+
|
|
434
|
+
Deliver compliance design document with:
|
|
435
|
+
- **Data Inventory** (data type, purpose, retention, legal basis)
|
|
436
|
+
- **Consent Flow Diagrams**
|
|
437
|
+
- **Privacy Impact Assessment**
|
|
438
|
+
- **User Rights Implementation Plan**
|
|
439
|
+
- **Compliance Checklist** (GDPR, CCPA, etc.)
|
|
440
|
+
- **Risk Assessment** (legal/financial exposure)
|
|
441
|
+
|
|
442
|
+
**Be thorough about compliance requirements. Note: This is technical guidance, not legal advice.**
|
|
443
|
+
|
|
444
|
+
## Minimal Return Pattern
|
|
445
|
+
|
|
446
|
+
Write full design to file, return only:
|
|
447
|
+
```
|
|
448
|
+
✓ Design complete. Saved to {filepath}
|
|
449
|
+
Key decisions: {1-2 sentence summary}
|
|
450
|
+
```
|