@fermindi/pwn-cli 0.5.0 → 0.6.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.
Files changed (21) hide show
  1. package/README.md +14 -10
  2. package/cli/batch.js +23 -10
  3. package/cli/index.js +2 -2
  4. package/cli/inject.js +3 -2
  5. package/cli/migrate.js +2 -2
  6. package/cli/mode.js +2 -2
  7. package/cli/status.js +1 -1
  8. package/cli/update.js +50 -6
  9. package/package.json +1 -1
  10. package/src/core/inject.js +25 -8
  11. package/src/core/validate.js +16 -1
  12. package/src/core/workspace.js +13 -11
  13. package/src/services/batch-service.js +78 -55
  14. package/templates/workspace/.ai/agents/claude.md +47 -146
  15. package/templates/workspace/.ai/memory/patterns.md +57 -11
  16. package/templates/workspace/.ai/tasks/active.md +1 -1
  17. package/templates/workspace/.ai/workflows/batch-task.md +43 -67
  18. package/templates/workspace/.claude/commands/mode.md +6 -5
  19. package/templates/workspace/.claude/commands/save.md +0 -42
  20. package/templates/workspace/.claude/settings.json +11 -2
  21. package/templates/workspace/.ai/tasks/backlog.md +0 -95
package/templates/workspace/.ai/tasks/backlog.md DELETED
@@ -1,95 +0,0 @@
1
- # Backlog
2
-
3
- This file contains prioritized future tasks not yet in active work.
4
-
5
- ## Format
6
-
7
- Tasks are listed in priority order (highest to lowest):
8
-
9
- ```markdown
10
- ### US-XXX: Task Title
11
- **Type:** Story | Bug | DevTask
12
- **Priority:** High | Medium | Low
13
- **Effort:** (T-shirt size: XS, S, M, L, XL)
14
- **Description:** What needs to be done
15
- **Acceptance Criteria:**
16
- - [ ] Criterion 1
17
- - [ ] Criterion 2
18
- **Dependencies:** (Other tasks needed first)
19
- **Notes:** Context, caveats, research needed
20
- ```
21
-
22
- ---
23
-
24
- ## Moving to Active
25
-
26
- When starting a backlog task:
27
-
28
- 1. Create issue/ticket in your tracking system
29
- 2. Move to `active.md` with checkbox
30
- 3. Assign team member
31
- 4. Update priority based on sprint plan
32
- 5. Reference in commit messages
33
-
34
- ---
35
-
36
- ## Adding New Tasks
37
-
38
- When new work is identified:
39
-
40
- 1. Assign next ID (US-XXX, BUG-XXX, etc.)
41
- 2. Add to appropriate section
42
- 3. Fill in all fields
43
- 4. Don't assign yet - wait for planning
44
- 5. Commit with message: `docs: add [ID] to backlog`
45
-
46
- ---
47
-
48
- ## Backlog Sections
49
-
50
- ### High Priority
51
- Work that should start soon. Review weekly.
52
-
53
- ### Medium Priority
54
- Important but can wait. Review biweekly.
55
-
56
- ### Low Priority
57
- Nice-to-have improvements. Review monthly.
58
-
59
- ### Roadmap (Future Phases)
60
- Longer-term projects for future planning.
61
-
62
- ---
63
-
64
- ## Template for New Backlog Item
65
-
66
- ```markdown
67
- ### US-XXX: [Title]
68
- **Type:** Story | Bug | DevTask
69
- **Priority:** High | Medium | Low
70
- **Effort:** S/M/L
71
- **Description:** (What and why)
72
- **Acceptance Criteria:**
73
- - [ ] (Specific, measurable outcome)
74
- **Dependencies:** (Other tasks)
75
- **Notes:** (Research, concerns, constraints)
76
- ```
77
-
78
- ---
79
-
80
- ## Management Guidelines
81
-
82
- - Groom backlog every sprint (remove duplicates, clarify)
83
- - Estimate effort using relative sizing (XS, S, M, L, XL)
84
- - Link related tasks together
85
- - Archive completed items with date + time spent
86
- - Keep description brief - link to external tickets for details
87
-
88
- ---
89
-
90
- ## Cleanup
91
-
92
- - Remove or update duplicates
93
- - Close blocked items after 30 days of no progress
94
- - Archive completed items to `completed/` section
95
- - Re-estimate if context changes significantly