@chief-clancy/terminal 0.1.3 → 0.1.5

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 (34) hide show
  1. package/dist/hooks/clancy-statusline.js +1 -1
  2. package/dist/installer/brief-content/brief-content.d.ts +62 -0
  3. package/dist/installer/brief-content/brief-content.d.ts.map +1 -0
  4. package/dist/installer/brief-content/brief-content.js +95 -0
  5. package/dist/installer/brief-content/brief-content.js.map +1 -0
  6. package/dist/installer/brief-content/index.d.ts +2 -0
  7. package/dist/installer/brief-content/index.d.ts.map +1 -0
  8. package/dist/installer/brief-content/index.js +2 -0
  9. package/dist/installer/brief-content/index.js.map +1 -0
  10. package/dist/installer/install/install.d.ts +8 -7
  11. package/dist/installer/install/install.d.ts.map +1 -1
  12. package/dist/installer/install/install.js +17 -18
  13. package/dist/installer/install/install.js.map +1 -1
  14. package/dist/installer/plan-content/index.d.ts +2 -0
  15. package/dist/installer/plan-content/index.d.ts.map +1 -0
  16. package/dist/installer/plan-content/index.js +2 -0
  17. package/dist/installer/plan-content/index.js.map +1 -0
  18. package/dist/installer/plan-content/plan-content.d.ts +55 -0
  19. package/dist/installer/plan-content/plan-content.d.ts.map +1 -0
  20. package/dist/installer/plan-content/plan-content.js +87 -0
  21. package/dist/installer/plan-content/plan-content.js.map +1 -0
  22. package/dist/installer/shared/fs-guards/fs-guards.d.ts +4 -0
  23. package/dist/installer/shared/fs-guards/fs-guards.d.ts.map +1 -1
  24. package/dist/installer/shared/fs-guards/fs-guards.js +13 -0
  25. package/dist/installer/shared/fs-guards/fs-guards.js.map +1 -1
  26. package/dist/installer/shared/fs-guards/index.d.ts +1 -1
  27. package/dist/installer/shared/fs-guards/index.d.ts.map +1 -1
  28. package/dist/installer/shared/fs-guards/index.js +1 -1
  29. package/dist/installer/shared/fs-guards/index.js.map +1 -1
  30. package/package.json +1 -1
  31. package/src/roles/planner/commands/plan.md +0 -22
  32. package/src/roles/planner/workflows/plan.md +0 -868
  33. package/src/roles/strategist/commands/brief.md +0 -29
  34. package/src/roles/strategist/workflows/brief.md +0 -1330
@@ -1,29 +0,0 @@
1
- # /clancy:brief
2
-
3
- Generate a strategic brief for a feature idea. Researches the codebase, grills you (or itself) on requirements, and produces a decomposition into actionable tickets.
4
-
5
- Accepts optional arguments:
6
-
7
- - **Board ticket:** `/clancy:brief PROJ-123`, `/clancy:brief #42`, `/clancy:brief ENG-42` — brief from a board ticket
8
- - **Inline text:** `/clancy:brief "Add dark mode"` — brief from a description
9
- - **From file:** `/clancy:brief --from docs/rfc.md` — brief from a local file
10
- - **Batch mode:** `/clancy:brief 3` — brief up to 3 tickets from the queue
11
- - **Fresh start:** `--fresh` — discard existing brief and start over
12
- - **Force web research:** `--research` — include web research in analysis
13
- - **AFK mode:** `--afk` — use AI-grill instead of human grill
14
- - **Epic hint:** `--epic PROJ-50 "Add dark mode"` — set parent for approve step
15
- - **List briefs:** `--list` — show inventory of existing briefs
16
-
17
- Examples:
18
-
19
- - `/clancy:brief` — interactive mode (prompt for idea)
20
- - `/clancy:brief PROJ-200` — brief a Jira ticket
21
- - `/clancy:brief #42` — brief a GitHub issue
22
- - `/clancy:brief ENG-42` — brief a Linear issue
23
- - `/clancy:brief "Add dark mode support"` — brief from inline text
24
- - `/clancy:brief --afk PROJ-200` — brief with AI-grill (no human questions)
25
- - `/clancy:brief --list` — show all briefs
26
-
27
- @.claude/clancy/workflows/brief.md
28
-
29
- Follow the brief workflow above. Research the codebase, conduct the grill phase, generate the brief, and save it locally. Do not create tickets — briefing only.