omgkit 2.1.0 → 2.2.0
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/package.json +1 -1
- package/plugin/skills/SKILL_STANDARDS.md +743 -0
- package/plugin/skills/databases/mongodb/SKILL.md +797 -28
- package/plugin/skills/databases/postgresql/SKILL.md +494 -18
- package/plugin/skills/databases/prisma/SKILL.md +776 -30
- package/plugin/skills/databases/redis/SKILL.md +885 -25
- package/plugin/skills/devops/aws/SKILL.md +686 -28
- package/plugin/skills/devops/docker/SKILL.md +466 -18
- package/plugin/skills/devops/github-actions/SKILL.md +684 -29
- package/plugin/skills/devops/kubernetes/SKILL.md +621 -24
- package/plugin/skills/frameworks/django/SKILL.md +920 -20
- package/plugin/skills/frameworks/express/SKILL.md +1361 -35
- package/plugin/skills/frameworks/fastapi/SKILL.md +1260 -33
- package/plugin/skills/frameworks/laravel/SKILL.md +1244 -31
- package/plugin/skills/frameworks/nestjs/SKILL.md +1005 -26
- package/plugin/skills/frameworks/nextjs/SKILL.md +407 -44
- package/plugin/skills/frameworks/rails/SKILL.md +594 -28
- package/plugin/skills/frameworks/react/SKILL.md +1006 -32
- package/plugin/skills/frameworks/spring/SKILL.md +528 -35
- package/plugin/skills/frameworks/vue/SKILL.md +1296 -27
- package/plugin/skills/frontend/accessibility/SKILL.md +1108 -34
- package/plugin/skills/frontend/frontend-design/SKILL.md +1304 -26
- package/plugin/skills/frontend/responsive/SKILL.md +847 -21
- package/plugin/skills/frontend/shadcn-ui/SKILL.md +976 -38
- package/plugin/skills/frontend/tailwindcss/SKILL.md +831 -35
- package/plugin/skills/frontend/threejs/SKILL.md +1298 -29
- package/plugin/skills/languages/javascript/SKILL.md +935 -31
- package/plugin/skills/languages/python/SKILL.md +489 -25
- package/plugin/skills/languages/typescript/SKILL.md +379 -30
- package/plugin/skills/methodology/brainstorming/SKILL.md +597 -23
- package/plugin/skills/methodology/defense-in-depth/SKILL.md +832 -34
- package/plugin/skills/methodology/dispatching-parallel-agents/SKILL.md +665 -31
- package/plugin/skills/methodology/executing-plans/SKILL.md +556 -24
- package/plugin/skills/methodology/finishing-development-branch/SKILL.md +595 -25
- package/plugin/skills/methodology/problem-solving/SKILL.md +429 -61
- package/plugin/skills/methodology/receiving-code-review/SKILL.md +536 -24
- package/plugin/skills/methodology/requesting-code-review/SKILL.md +632 -21
- package/plugin/skills/methodology/root-cause-tracing/SKILL.md +641 -30
- package/plugin/skills/methodology/sequential-thinking/SKILL.md +262 -3
- package/plugin/skills/methodology/systematic-debugging/SKILL.md +571 -32
- package/plugin/skills/methodology/test-driven-development/SKILL.md +779 -24
- package/plugin/skills/methodology/testing-anti-patterns/SKILL.md +691 -29
- package/plugin/skills/methodology/token-optimization/SKILL.md +598 -29
- package/plugin/skills/methodology/verification-before-completion/SKILL.md +543 -22
- package/plugin/skills/methodology/writing-plans/SKILL.md +590 -18
- package/plugin/skills/omega/omega-architecture/SKILL.md +838 -39
- package/plugin/skills/omega/omega-coding/SKILL.md +636 -39
- package/plugin/skills/omega/omega-sprint/SKILL.md +855 -48
- package/plugin/skills/omega/omega-testing/SKILL.md +940 -41
- package/plugin/skills/omega/omega-thinking/SKILL.md +703 -50
- package/plugin/skills/security/better-auth/SKILL.md +1065 -28
- package/plugin/skills/security/oauth/SKILL.md +968 -31
- package/plugin/skills/security/owasp/SKILL.md +894 -33
- package/plugin/skills/testing/playwright/SKILL.md +764 -38
- package/plugin/skills/testing/pytest/SKILL.md +873 -36
- package/plugin/skills/testing/vitest/SKILL.md +980 -35
|
@@ -1,34 +1,566 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: executing-plans
|
|
3
|
-
description:
|
|
3
|
+
description: Systematic plan execution with progress tracking, quality gates, and blocker resolution
|
|
4
|
+
category: methodology
|
|
5
|
+
triggers:
|
|
6
|
+
- executing plans
|
|
7
|
+
- following plan
|
|
8
|
+
- implementation
|
|
9
|
+
- executing tasks
|
|
10
|
+
- working on plan
|
|
11
|
+
- task execution
|
|
4
12
|
---
|
|
5
13
|
|
|
6
|
-
# Executing Plans
|
|
14
|
+
# Executing Plans
|
|
7
15
|
|
|
8
|
-
|
|
9
|
-
1. Read the plan completely
|
|
10
|
-
2. Verify understanding
|
|
11
|
-
3. Execute tasks in order
|
|
12
|
-
4. Check off completed tasks
|
|
13
|
-
5. Report blockers immediately
|
|
16
|
+
Master **systematic plan execution** with disciplined task progression, quality validation, and clear communication. This skill ensures plans are executed efficiently while maintaining high standards and adapting to discoveries.
|
|
14
17
|
|
|
15
|
-
##
|
|
16
|
-
1. Read task description
|
|
17
|
-
2. Navigate to code location
|
|
18
|
-
3. Implement change
|
|
19
|
-
4. Verify it works
|
|
20
|
-
5. Mark complete
|
|
21
|
-
6. Proceed to next
|
|
18
|
+
## Purpose
|
|
22
19
|
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
-
|
|
26
|
-
-
|
|
20
|
+
Transform plans into successful outcomes:
|
|
21
|
+
|
|
22
|
+
- Execute tasks in optimal sequence
|
|
23
|
+
- Maintain momentum through blockers
|
|
24
|
+
- Validate quality at each checkpoint
|
|
25
|
+
- Track and communicate progress
|
|
26
|
+
- Adapt to new information gracefully
|
|
27
|
+
- Complete work to high standards
|
|
28
|
+
- Document learnings for future reference
|
|
29
|
+
|
|
30
|
+
## Features
|
|
31
|
+
|
|
32
|
+
### 1. Execution Workflow
|
|
33
|
+
|
|
34
|
+
```markdown
|
|
35
|
+
## Plan Execution Process
|
|
36
|
+
|
|
37
|
+
┌───────────────────────────────────────────────────────────────┐
|
|
38
|
+
│ START EXECUTION │
|
|
39
|
+
└───────────────────────────────────────────────────────────────┘
|
|
40
|
+
│
|
|
41
|
+
▼
|
|
42
|
+
┌───────────────────────────────────────────────────────────────┐
|
|
43
|
+
│ PHASE 1: PREPARATION │
|
|
44
|
+
│ ───────────────────── │
|
|
45
|
+
│ □ Read entire plan thoroughly │
|
|
46
|
+
│ □ Verify understanding of goals │
|
|
47
|
+
│ □ Check all dependencies are available │
|
|
48
|
+
│ □ Set up development environment │
|
|
49
|
+
│ □ Identify potential blockers early │
|
|
50
|
+
│ □ Confirm with stakeholders if unclear │
|
|
51
|
+
└───────────────────────────────────────────────────────────────┘
|
|
52
|
+
│
|
|
53
|
+
▼
|
|
54
|
+
┌───────────────────────────────────────────────────────────────┐
|
|
55
|
+
│ PHASE 2: EXECUTE TASK │
|
|
56
|
+
│ ───────────────────── │
|
|
57
|
+
│ For each task in sequence: │
|
|
58
|
+
│ │
|
|
59
|
+
│ 1. READ: Understand task requirements │
|
|
60
|
+
│ └─ What exactly needs to be done? │
|
|
61
|
+
│ └─ What are the acceptance criteria? │
|
|
62
|
+
│ └─ What files/locations are involved? │
|
|
63
|
+
│ │
|
|
64
|
+
│ 2. NAVIGATE: Go to code location │
|
|
65
|
+
│ └─ Open specified files │
|
|
66
|
+
│ └─ Understand existing code │
|
|
67
|
+
│ └─ Identify integration points │
|
|
68
|
+
│ │
|
|
69
|
+
│ 3. IMPLEMENT: Make the changes │
|
|
70
|
+
│ └─ Write minimal code to satisfy criteria │
|
|
71
|
+
│ └─ Follow coding standards │
|
|
72
|
+
│ └─ Add appropriate tests │
|
|
73
|
+
│ │
|
|
74
|
+
│ 4. VERIFY: Confirm it works │
|
|
75
|
+
│ └─ Run relevant tests │
|
|
76
|
+
│ └─ Manual verification if needed │
|
|
77
|
+
│ └─ Check edge cases │
|
|
78
|
+
│ │
|
|
79
|
+
│ 5. COMPLETE: Mark task done │
|
|
80
|
+
│ └─ Update task status │
|
|
81
|
+
│ └─ Note any deviations │
|
|
82
|
+
│ └─ Proceed to next task │
|
|
83
|
+
└───────────────────────────────────────────────────────────────┘
|
|
84
|
+
│
|
|
85
|
+
▼
|
|
86
|
+
┌───────────────────────────────────────────────────────────────┐
|
|
87
|
+
│ PHASE 3: QUALITY GATES │
|
|
88
|
+
│ ────────────────────── │
|
|
89
|
+
│ │
|
|
90
|
+
│ After EACH task: │
|
|
91
|
+
│ □ Does implementation match acceptance criteria? │
|
|
92
|
+
│ □ Do tests pass? │
|
|
93
|
+
│ □ Any regressions introduced? │
|
|
94
|
+
│ │
|
|
95
|
+
│ After EACH phase/milestone: │
|
|
96
|
+
│ □ Run full test suite │
|
|
97
|
+
│ □ Code review (self or peer) │
|
|
98
|
+
│ □ Update progress report │
|
|
99
|
+
│ │
|
|
100
|
+
│ Before COMPLETION: │
|
|
101
|
+
│ □ All tasks completed │
|
|
102
|
+
│ □ All tests passing │
|
|
103
|
+
│ □ Documentation updated │
|
|
104
|
+
│ □ Ready for final review │
|
|
105
|
+
└───────────────────────────────────────────────────────────────┘
|
|
106
|
+
│
|
|
107
|
+
▼
|
|
108
|
+
┌───────────────────────────────────────────────────────────────┐
|
|
109
|
+
│ PLAN COMPLETE │
|
|
110
|
+
└───────────────────────────────────────────────────────────────┘
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
### 2. Task Execution Checklist
|
|
114
|
+
|
|
115
|
+
```markdown
|
|
116
|
+
## Per-Task Execution Template
|
|
117
|
+
|
|
118
|
+
### Task: [TASK-ID] - [Task Name]
|
|
119
|
+
|
|
120
|
+
#### Before Starting
|
|
121
|
+
- [ ] Read task description completely
|
|
122
|
+
- [ ] Understand acceptance criteria
|
|
123
|
+
- [ ] Check dependencies completed
|
|
124
|
+
- [ ] No blockers present
|
|
125
|
+
- [ ] Time estimate reasonable
|
|
126
|
+
|
|
127
|
+
#### During Implementation
|
|
128
|
+
- [ ] Navigate to specified files
|
|
129
|
+
- [ ] Understand existing code context
|
|
130
|
+
- [ ] Implement changes incrementally
|
|
131
|
+
- [ ] Write tests alongside code
|
|
132
|
+
- [ ] Follow style guide
|
|
133
|
+
|
|
134
|
+
#### After Completion
|
|
135
|
+
- [ ] All acceptance criteria met
|
|
136
|
+
- [ ] Tests pass locally
|
|
137
|
+
- [ ] No lint/type errors
|
|
138
|
+
- [ ] Self-review done
|
|
139
|
+
- [ ] Task marked complete
|
|
140
|
+
|
|
141
|
+
#### Notes
|
|
142
|
+
- Started: [Time]
|
|
143
|
+
- Completed: [Time]
|
|
144
|
+
- Actual vs Estimated: [X hours vs Y hours]
|
|
145
|
+
- Deviations: [Any changes from plan]
|
|
146
|
+
- Learnings: [Anything useful discovered]
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
### 3. Progress Tracking
|
|
150
|
+
|
|
151
|
+
```markdown
|
|
152
|
+
## Progress Report Templates
|
|
153
|
+
|
|
154
|
+
### Quick Status Update
|
|
155
|
+
```markdown
|
|
156
|
+
## Status: [Date Time]
|
|
157
|
+
|
|
158
|
+
### Summary
|
|
159
|
+
- ✅ Completed: [N] tasks
|
|
160
|
+
- 🔄 In Progress: [Task name]
|
|
161
|
+
- ⏳ Remaining: [M] tasks
|
|
162
|
+
- 🚫 Blockers: [None | Description]
|
|
163
|
+
|
|
164
|
+
### ETA
|
|
165
|
+
On track for [original date] | Delayed by [reason]
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
### Detailed Progress Report
|
|
169
|
+
```markdown
|
|
170
|
+
## Progress Report: [Plan Name]
|
|
171
|
+
|
|
172
|
+
### Overview
|
|
173
|
+
- Start Date: [Date]
|
|
174
|
+
- Target Date: [Date]
|
|
175
|
+
- Current Status: On Track | At Risk | Blocked | Ahead
|
|
176
|
+
|
|
177
|
+
### Completed Tasks (X/Y)
|
|
178
|
+
| Task | Status | Notes |
|
|
179
|
+
|------|--------|-------|
|
|
180
|
+
| [Task 1] | ✅ | Completed as planned |
|
|
181
|
+
| [Task 2] | ✅ | Required API change |
|
|
182
|
+
| [Task 3] | ⏭️ | Skipped - not needed |
|
|
183
|
+
|
|
184
|
+
### Current Task
|
|
185
|
+
**[Task 4]:** [Description]
|
|
186
|
+
- Started: [Time]
|
|
187
|
+
- Progress: ~60%
|
|
188
|
+
- Expected completion: [Time]
|
|
189
|
+
- Notes: [Any observations]
|
|
190
|
+
|
|
191
|
+
### Remaining Tasks
|
|
192
|
+
| Task | Dependencies | Estimate | Risk |
|
|
193
|
+
|------|--------------|----------|------|
|
|
194
|
+
| [Task 5] | Task 4 | 2h | Low |
|
|
195
|
+
| [Task 6] | Task 5 | 1h | Low |
|
|
196
|
+
| [Task 7] | Task 6 | 4h | Medium |
|
|
197
|
+
|
|
198
|
+
### Blockers & Risks
|
|
199
|
+
| Issue | Impact | Mitigation | Owner |
|
|
200
|
+
|-------|--------|------------|-------|
|
|
201
|
+
| [Issue] | [High/Med/Low] | [Action] | [Name] |
|
|
202
|
+
|
|
203
|
+
### Decisions Made
|
|
204
|
+
1. **[Decision]**: [Rationale]
|
|
205
|
+
|
|
206
|
+
### Help Needed
|
|
207
|
+
- [ ] [Request for assistance]
|
|
208
|
+
|
|
209
|
+
### Next Update
|
|
210
|
+
[Scheduled time for next update]
|
|
211
|
+
```
|
|
212
|
+
|
|
213
|
+
### Visual Progress Board
|
|
214
|
+
```
|
|
215
|
+
Phase 1: Setup ████████████████████ 100%
|
|
216
|
+
Phase 2: Core Logic ██████████████░░░░░░ 70%
|
|
217
|
+
Phase 3: Integration ░░░░░░░░░░░░░░░░░░░░ 0%
|
|
218
|
+
Phase 4: Testing ░░░░░░░░░░░░░░░░░░░░ 0%
|
|
219
|
+
|
|
220
|
+
Overall: ███████████░░░░░░░░░ 55%
|
|
221
|
+
```
|
|
222
|
+
|
|
223
|
+
### 4. Blocker Resolution
|
|
224
|
+
|
|
225
|
+
```markdown
|
|
226
|
+
## Blocker Management Protocol
|
|
227
|
+
|
|
228
|
+
### Blocker Classification
|
|
229
|
+
|
|
230
|
+
| Type | Example | Resolution Approach |
|
|
231
|
+
|------|---------|---------------------|
|
|
232
|
+
| Technical | Unexpected API behavior | Debug, research, escalate |
|
|
233
|
+
| Dependency | Waiting on other task | Parallel work, resequence |
|
|
234
|
+
| Knowledge | Don't know how to do X | Research, ask, pair |
|
|
235
|
+
| Access | Missing permissions | Request access, escalate |
|
|
236
|
+
| External | Third-party down | Wait, workaround, escalate |
|
|
237
|
+
| Scope | Requirements unclear | Clarify with stakeholder |
|
|
238
|
+
|
|
239
|
+
### Blocker Response Process
|
|
240
|
+
|
|
241
|
+
```
|
|
242
|
+
BLOCKER DETECTED
|
|
243
|
+
│
|
|
244
|
+
▼
|
|
245
|
+
┌─────────────────────────────────────────────┐
|
|
246
|
+
│ 1. DOCUMENT immediately │
|
|
247
|
+
│ - What is blocked? │
|
|
248
|
+
│ - Why is it blocked? │
|
|
249
|
+
│ - When did it start? │
|
|
250
|
+
└─────────────────────────────────────────────┘
|
|
251
|
+
│
|
|
252
|
+
▼
|
|
253
|
+
┌─────────────────────────────────────────────┐
|
|
254
|
+
│ 2. ASSESS impact │
|
|
255
|
+
│ - Critical path affected? │
|
|
256
|
+
│ - Other tasks dependent? │
|
|
257
|
+
│ - Time sensitive? │
|
|
258
|
+
└─────────────────────────────────────────────┘
|
|
259
|
+
│
|
|
260
|
+
▼
|
|
261
|
+
┌─────────────────────────────────────────────┐
|
|
262
|
+
│ 3. ATTEMPT resolution (15-30 min) │
|
|
263
|
+
│ - Quick research │
|
|
264
|
+
│ - Alternative approach │
|
|
265
|
+
│ - Workaround possible? │
|
|
266
|
+
└─────────────────────────────────────────────┘
|
|
267
|
+
│
|
|
268
|
+
├──► RESOLVED ──► Continue execution
|
|
269
|
+
│
|
|
270
|
+
▼
|
|
271
|
+
┌─────────────────────────────────────────────┐
|
|
272
|
+
│ 4. ESCALATE if not resolved │
|
|
273
|
+
│ - Report to lead/stakeholder │
|
|
274
|
+
│ - Include: issue, attempts, ask │
|
|
275
|
+
└─────────────────────────────────────────────┘
|
|
276
|
+
│
|
|
277
|
+
▼
|
|
278
|
+
┌─────────────────────────────────────────────┐
|
|
279
|
+
│ 5. WORK AROUND while waiting │
|
|
280
|
+
│ - Move to non-blocked tasks │
|
|
281
|
+
│ - Document workaround if temporary │
|
|
282
|
+
└─────────────────────────────────────────────┘
|
|
283
|
+
```
|
|
284
|
+
|
|
285
|
+
### Blocker Report Template
|
|
286
|
+
```markdown
|
|
287
|
+
## Blocker Report
|
|
288
|
+
|
|
289
|
+
### Issue
|
|
290
|
+
[Clear description of the blocker]
|
|
291
|
+
|
|
292
|
+
### Impact
|
|
293
|
+
- **Blocked tasks:** [List of affected tasks]
|
|
294
|
+
- **Timeline impact:** [Delay estimate]
|
|
295
|
+
- **Severity:** Critical | High | Medium | Low
|
|
296
|
+
|
|
297
|
+
### Attempted Solutions
|
|
298
|
+
1. [What was tried]
|
|
299
|
+
- Result: [Outcome]
|
|
300
|
+
2. [What was tried]
|
|
301
|
+
- Result: [Outcome]
|
|
302
|
+
|
|
303
|
+
### Request
|
|
304
|
+
[Specific help or decision needed]
|
|
305
|
+
|
|
306
|
+
### Workaround Available?
|
|
307
|
+
[Yes/No] - [Description if yes]
|
|
308
|
+
|
|
309
|
+
### Timeline
|
|
310
|
+
- Blocker detected: [Time]
|
|
311
|
+
- Resolution needed by: [Time]
|
|
312
|
+
```
|
|
313
|
+
|
|
314
|
+
### 5. Quality Gates Implementation
|
|
315
|
+
|
|
316
|
+
```markdown
|
|
317
|
+
## Quality Gate Checkpoints
|
|
318
|
+
|
|
319
|
+
### After Each Task
|
|
320
|
+
```bash
|
|
321
|
+
# Quick validation script
|
|
322
|
+
npm run lint
|
|
323
|
+
npm run typecheck
|
|
324
|
+
npm run test -- --related
|
|
325
|
+
```
|
|
27
326
|
|
|
28
|
-
## Reporting
|
|
29
327
|
```markdown
|
|
30
|
-
|
|
31
|
-
-
|
|
32
|
-
-
|
|
33
|
-
-
|
|
328
|
+
Quality Checklist:
|
|
329
|
+
- [ ] Code compiles without errors
|
|
330
|
+
- [ ] Linting passes
|
|
331
|
+
- [ ] Relevant tests pass
|
|
332
|
+
- [ ] No console errors/warnings
|
|
333
|
+
- [ ] Self-review completed
|
|
34
334
|
```
|
|
335
|
+
|
|
336
|
+
### After Each Phase
|
|
337
|
+
```bash
|
|
338
|
+
# Phase validation script
|
|
339
|
+
npm run lint
|
|
340
|
+
npm run typecheck
|
|
341
|
+
npm run test
|
|
342
|
+
npm run build
|
|
343
|
+
```
|
|
344
|
+
|
|
345
|
+
```markdown
|
|
346
|
+
Phase Checklist:
|
|
347
|
+
- [ ] All phase tasks complete
|
|
348
|
+
- [ ] Full test suite passes
|
|
349
|
+
- [ ] Build succeeds
|
|
350
|
+
- [ ] No new TODO comments left
|
|
351
|
+
- [ ] Code reviewed
|
|
352
|
+
- [ ] Documentation updated
|
|
353
|
+
```
|
|
354
|
+
|
|
355
|
+
### Before Final Completion
|
|
356
|
+
```bash
|
|
357
|
+
# Final validation script
|
|
358
|
+
npm run lint
|
|
359
|
+
npm run typecheck
|
|
360
|
+
npm run test -- --coverage
|
|
361
|
+
npm run build
|
|
362
|
+
npm run e2e
|
|
363
|
+
```
|
|
364
|
+
|
|
365
|
+
```markdown
|
|
366
|
+
Completion Checklist:
|
|
367
|
+
- [ ] All planned tasks complete
|
|
368
|
+
- [ ] All tests pass (unit, integration, e2e)
|
|
369
|
+
- [ ] Coverage meets threshold
|
|
370
|
+
- [ ] Build succeeds
|
|
371
|
+
- [ ] Performance acceptable
|
|
372
|
+
- [ ] Documentation complete
|
|
373
|
+
- [ ] Reviewed and approved
|
|
374
|
+
- [ ] Ready for deployment
|
|
375
|
+
```
|
|
376
|
+
|
|
377
|
+
### 6. Deviation Handling
|
|
378
|
+
|
|
379
|
+
```markdown
|
|
380
|
+
## Handling Plan Deviations
|
|
381
|
+
|
|
382
|
+
### Types of Deviations
|
|
383
|
+
|
|
384
|
+
| Type | Example | Response |
|
|
385
|
+
|------|---------|----------|
|
|
386
|
+
| Scope Addition | New requirement discovered | Document, assess, negotiate |
|
|
387
|
+
| Scope Reduction | Feature not needed | Document, skip, update plan |
|
|
388
|
+
| Technical Change | Different approach needed | Assess impact, update plan |
|
|
389
|
+
| Estimate Change | Task taking longer | Report, adjust timeline |
|
|
390
|
+
| Dependency Change | Order needs to change | Resequence, update plan |
|
|
391
|
+
|
|
392
|
+
### Deviation Decision Tree
|
|
393
|
+
|
|
394
|
+
```
|
|
395
|
+
DEVIATION DETECTED
|
|
396
|
+
│
|
|
397
|
+
├── Is it blocking progress?
|
|
398
|
+
│ ├── YES → Immediate resolution needed
|
|
399
|
+
│ │ └── Escalate if not resolvable
|
|
400
|
+
│ └── NO → Document and continue
|
|
401
|
+
│
|
|
402
|
+
├── Does it change scope?
|
|
403
|
+
│ ├── YES → Stakeholder approval needed
|
|
404
|
+
│ │ └── Update plan if approved
|
|
405
|
+
│ └── NO → Proceed with adjustment
|
|
406
|
+
│
|
|
407
|
+
└── Does it change timeline?
|
|
408
|
+
├── YES → Report new estimate
|
|
409
|
+
│ └── Negotiate if critical
|
|
410
|
+
└── NO → Continue execution
|
|
411
|
+
```
|
|
412
|
+
|
|
413
|
+
### Deviation Documentation
|
|
414
|
+
```markdown
|
|
415
|
+
## Plan Deviation Record
|
|
416
|
+
|
|
417
|
+
### Original Plan
|
|
418
|
+
[What was originally planned]
|
|
419
|
+
|
|
420
|
+
### Deviation
|
|
421
|
+
[What actually happened/needs to happen]
|
|
422
|
+
|
|
423
|
+
### Reason
|
|
424
|
+
[Why the deviation occurred]
|
|
425
|
+
|
|
426
|
+
### Impact
|
|
427
|
+
- Timeline: [No change | +X hours/days]
|
|
428
|
+
- Scope: [No change | Added/Removed X]
|
|
429
|
+
- Quality: [No change | Trade-off made]
|
|
430
|
+
|
|
431
|
+
### Decision
|
|
432
|
+
[Approved/Rejected] by [Name] on [Date]
|
|
433
|
+
|
|
434
|
+
### Updated Plan
|
|
435
|
+
[Link to updated plan or inline changes]
|
|
436
|
+
```
|
|
437
|
+
```
|
|
438
|
+
|
|
439
|
+
## Use Cases
|
|
440
|
+
|
|
441
|
+
### Feature Implementation Execution
|
|
442
|
+
|
|
443
|
+
```markdown
|
|
444
|
+
## Execution Log: User Profile Feature
|
|
445
|
+
|
|
446
|
+
### Preparation (Day 1, 9:00 AM)
|
|
447
|
+
✅ Read plan completely
|
|
448
|
+
✅ Environment setup verified
|
|
449
|
+
✅ Dependencies checked (auth service deployed)
|
|
450
|
+
✅ Questions clarified with PM
|
|
451
|
+
|
|
452
|
+
### Task 1: Database Migration (9:30 AM - 10:00 AM)
|
|
453
|
+
**Status:** ✅ Complete
|
|
454
|
+
|
|
455
|
+
Actions:
|
|
456
|
+
1. Created migration file
|
|
457
|
+
2. Added profile fields to users table
|
|
458
|
+
3. Ran migration locally
|
|
459
|
+
4. Verified schema
|
|
460
|
+
|
|
461
|
+
Verification:
|
|
462
|
+
- ✅ Migration applies cleanly
|
|
463
|
+
- ✅ Rollback works
|
|
464
|
+
- ✅ No existing data affected
|
|
465
|
+
|
|
466
|
+
### Task 2: API Endpoint (10:00 AM - 11:30 AM)
|
|
467
|
+
**Status:** ✅ Complete
|
|
468
|
+
|
|
469
|
+
Actions:
|
|
470
|
+
1. Created ProfileController
|
|
471
|
+
2. Implemented GET /profile
|
|
472
|
+
3. Implemented PUT /profile
|
|
473
|
+
4. Added validation
|
|
474
|
+
|
|
475
|
+
Verification:
|
|
476
|
+
- ✅ Unit tests pass
|
|
477
|
+
- ✅ Tested with Postman
|
|
478
|
+
- ✅ Error cases handled
|
|
479
|
+
|
|
480
|
+
### Task 3: Frontend Form (11:30 AM - 12:30 PM)
|
|
481
|
+
**Status:** 🔄 In Progress
|
|
482
|
+
|
|
483
|
+
Blocker Encountered (12:00 PM):
|
|
484
|
+
- Issue: Form library version conflict
|
|
485
|
+
- Impact: 30 min delay
|
|
486
|
+
- Resolution: Upgraded to compatible version
|
|
487
|
+
|
|
488
|
+
### Lunch Break (12:30 PM - 1:30 PM)
|
|
489
|
+
|
|
490
|
+
### Task 3: Frontend Form (Continued) (1:30 PM - 2:30 PM)
|
|
491
|
+
**Status:** ✅ Complete
|
|
492
|
+
|
|
493
|
+
Verification:
|
|
494
|
+
- ✅ Form renders correctly
|
|
495
|
+
- ✅ Validation works
|
|
496
|
+
- ✅ Submit updates profile
|
|
497
|
+
- ✅ Error states display
|
|
498
|
+
|
|
499
|
+
### Task 4: Integration Tests (2:30 PM - 3:30 PM)
|
|
500
|
+
**Status:** ✅ Complete
|
|
501
|
+
|
|
502
|
+
### Phase 1 Quality Gate (3:30 PM)
|
|
503
|
+
- ✅ All tests pass
|
|
504
|
+
- ✅ Lint clean
|
|
505
|
+
- ✅ Build succeeds
|
|
506
|
+
- ✅ Self-review done
|
|
507
|
+
|
|
508
|
+
### Progress Report (3:30 PM)
|
|
509
|
+
```markdown
|
|
510
|
+
Completed: 4/6 tasks
|
|
511
|
+
In Progress: None
|
|
512
|
+
Remaining: 2 tasks (E2E, Documentation)
|
|
513
|
+
Blockers: None
|
|
514
|
+
ETA: On track for EOD
|
|
515
|
+
```
|
|
516
|
+
|
|
517
|
+
### Task 5 & 6: (3:30 PM - 5:00 PM)
|
|
518
|
+
[Continued execution...]
|
|
519
|
+
|
|
520
|
+
### Final Quality Gate (5:00 PM)
|
|
521
|
+
- ✅ All tasks complete
|
|
522
|
+
- ✅ All tests pass
|
|
523
|
+
- ✅ Documentation updated
|
|
524
|
+
- ✅ Ready for review
|
|
525
|
+
|
|
526
|
+
### Completion Summary
|
|
527
|
+
- Planned: 8 hours
|
|
528
|
+
- Actual: 7.5 hours
|
|
529
|
+
- Deviations: 1 (library upgrade)
|
|
530
|
+
- Learnings: Document library versions
|
|
531
|
+
```
|
|
532
|
+
|
|
533
|
+
## Best Practices
|
|
534
|
+
|
|
535
|
+
### Do's
|
|
536
|
+
|
|
537
|
+
- Read the entire plan before starting
|
|
538
|
+
- Verify understanding of each task
|
|
539
|
+
- Execute tasks in sequence unless parallel safe
|
|
540
|
+
- Validate after each task completion
|
|
541
|
+
- Report blockers immediately
|
|
542
|
+
- Document deviations as they occur
|
|
543
|
+
- Take notes for future reference
|
|
544
|
+
- Communicate progress regularly
|
|
545
|
+
- Ask questions early
|
|
546
|
+
- Complete fully before marking done
|
|
547
|
+
|
|
548
|
+
### Don'ts
|
|
549
|
+
|
|
550
|
+
- Don't skip the preparation phase
|
|
551
|
+
- Don't assume task requirements
|
|
552
|
+
- Don't ignore quality gates
|
|
553
|
+
- Don't hide blockers or delays
|
|
554
|
+
- Don't deviate without documenting
|
|
555
|
+
- Don't rush quality for speed
|
|
556
|
+
- Don't forget to update status
|
|
557
|
+
- Don't leave tasks partially done
|
|
558
|
+
- Don't skip testing steps
|
|
559
|
+
- Don't ignore learnings
|
|
560
|
+
|
|
561
|
+
## References
|
|
562
|
+
|
|
563
|
+
- [Getting Things Done - David Allen](https://gettingthingsdone.com/)
|
|
564
|
+
- [The Checklist Manifesto - Atul Gawande](http://atulgawande.com/book/the-checklist-manifesto/)
|
|
565
|
+
- [Agile Project Management](https://www.atlassian.com/agile/project-management)
|
|
566
|
+
- [Kanban Method](https://kanbanize.com/kanban-resources/getting-started/what-is-kanban)
|