tribunal-kit 4.5.1 → 4.6.1

package/.agent/workflows/brainstorm.md

@@ -1,110 +1,134 @@
----
-description: Structured brainstorming for projects and features. Uses Socratic questioning to explore multiple options before committing to an approach. No implementation during this phase — only exploration.
----
-
-# /brainstorm — Structured Idea Exploration
-
-$ARGUMENTS
-
----
-
-## When to Use /brainstorm
-
-|Use `/brainstorm` when...|Move to...|
-|:---|:---|
-|Multiple valid approaches exist|After decision → `/plan`|
-|You're unsure of the best architecture|After plan approval → `/generate`|
-|Exploring tradeoffs before committing|Confirmed approach → `/create`|
-|Looking for second opinions on design||
-
----
-
-## Phase 1 — Question First
-
-Before generating ideas, ask 3 clarifying questions:
-
-```
-1. What constraint is non-negotiable? (timeline, tech stack, cost, performance)
-2. What has already been tried and ruled out?
-3. What does "success" look like for this decision?
-```
-
----
-
-## Phase 2 — Generate 3 Distinct Options
-
-Present minimum 3 meaningfully different approaches:
-
-```
-Option A: [Conservative approach]
-  Pros: [why this works]
-  Cons: [what it sacrifices]
-  Effort: [Low / Medium / High]
-  Best for: [when this is the right choice]
-
-Option B: [Balanced approach]
-  Pros: [why this works]
-  Cons: [what it sacrifices]
-  Effort: [Low / Medium / High]
-  Best for: [when this is the right choice]
-
-Option C: [Ambitious approach]
-  Pros: [why this works]
-  Cons: [what it sacrifices]
-  Effort: [Low / Medium / High]
-  Best for: [when this is the right choice]
-```
-
----
-
-## Phase 3 — Socratic Analysis
-
-After presenting options, probe with questions that reveal hidden tradeoffs:
-
-```
-□ What happens when this scales to 10x current load?
-□ What's the maintenance cost 12 months from now?
-□ Which option fails most gracefully under the worst case?
-□ Which option are you most likely to regret?
-□ What's the opportunity cost of each option?
-```
-
----
-
-## Phase 4 — Recommendation (Evidence-Based)
-
-After exploration, state a recommendation:
-
-```
-Recommended: Option [B]
-
-Reasoning:
-- [specific reason 1 tied to stated constraints]
-- [specific reason 2]
-- [specific tradeoff you're accepting and why]
-
-NOT recommended because [reason Option A/C is worse for this specific context]
-```
-
----
-
-## Brainstorm Guard
-
-```
-❌ Never present a single option as if it's the only choice
-❌ Never recommend without explaining WHY in terms of the stated constraints
-❌ Never skip the Socratic probing — it surfaces assumptions
-❌ Never proceed to implementation in /brainstorm mode — use /plan after
-```
-
----
-
-## Usage Examples
-
-```
-/brainstorm real-time collaboration: WebSockets vs Server-Sent Events vs CRDTs
-/brainstorm caching strategy: Redis vs in-memory vs CDN for our API responses
-/brainstorm auth: next-auth vs Clerk vs custom JWT for our SaaS app
-/brainstorm state management: Zustand vs Redux vs TanStack Query
-/brainstorm monolith vs microservices for our current team size
-```
+---
+description: Structured brainstorming for projects and features. Uses Socratic questioning to explore multiple options before committing to an approach. No implementation during this phase — only exploration.
+required-skills: brainstorming
+---
+
+# /brainstorm — Structured Idea Exploration
+
+$ARGUMENTS
+
+---
+
+## $CONTEXT_REQUIRED
+
+```
+Read BEFORE generating any options:
+□ package.json         → Understand existing stack constraints
+□ tsconfig.json        → Understand language/framework version
+□ Project root listing → Understand project structure and scale
+□ .agent/skills/brainstorming/SKILL.md → Load domain question banks
+```
+
+---
+
+## When to Use /brainstorm
+
+| Use `/brainstorm` when...              | Move to...                        |
+| :------------------------------------- | :-------------------------------- |
+| Multiple valid approaches exist        | After decision → `/plan`          |
+| You're unsure of the best architecture | After plan approval → `/generate` |
+| Exploring tradeoffs before committing  | Confirmed approach → `/create`    |
+| Looking for second opinions on design  |                                   |
+
+---
+
+## Phase 1 — Question First
+
+Before generating ideas, ask 3 clarifying questions:
+
+```
+1. What constraint is non-negotiable? (timeline, tech stack, cost, performance)
+2. What has already been tried and ruled out?
+3. What does "success" look like for this decision?
+```
+
+---
+
+## Phase 2 — Generate 3 Distinct Options
+
+Present minimum 3 meaningfully different approaches:
+
+```
+Option A: [Conservative approach]
+  Pros: [why this works]
+  Cons: [what it sacrifices]
+  Effort: [Low / Medium / High]
+  Best for: [when this is the right choice]
+
+Option B: [Balanced approach]
+  Pros: [why this works]
+  Cons: [what it sacrifices]
+  Effort: [Low / Medium / High]
+  Best for: [when this is the right choice]
+
+Option C: [Ambitious approach]
+  Pros: [why this works]
+  Cons: [what it sacrifices]
+  Effort: [Low / Medium / High]
+  Best for: [when this is the right choice]
+```
+
+---
+
+## Phase 3 — Socratic Analysis
+
+After presenting options, probe with questions that reveal hidden tradeoffs:
+
+```
+□ What happens when this scales to 10x current load?
+□ What's the maintenance cost 12 months from now?
+□ Which option fails most gracefully under the worst case?
+□ Which option are you most likely to regret?
+□ What's the opportunity cost of each option?
+```
+
+---
+
+## Phase 4 — Recommendation (Evidence-Based)
+
+After exploration, state a recommendation:
+
+```
+Recommended: Option [B]
+
+Reasoning:
+- [specific reason 1 tied to stated constraints]
+- [specific reason 2]
+- [specific tradeoff you're accepting and why]
+
+NOT recommended because [reason Option A/C is worse for this specific context]
+```
+
+---
+
+## Brainstorm Guard
+
+```
+❌ Never present a single option as if it's the only choice
+❌ Never recommend without explaining WHY in terms of the stated constraints
+❌ Never skip the Socratic probing — it surfaces assumptions
+❌ Never proceed to implementation in /brainstorm mode — use /plan after
+```
+
+---
+
+## After /brainstorm — Next Steps
+
+| Outcome                                    | Next Command                              |
+| :----------------------------------------- | :---------------------------------------- |
+| Decision made, ready to plan               | → `/plan` with the Distilled Assertions   |
+| Decision made, ready to build from scratch | → `/create` with chosen stack             |
+| Need more exploration in a specific domain | → `/brainstorm` again with narrower scope |
+| Ready to generate a specific piece         | → `/generate` for a focused snippet       |
+
+---
+
+## Usage Examples
+
+```
+/brainstorm real-time collaboration: WebSockets vs Server-Sent Events vs CRDTs
+/brainstorm caching strategy: Redis vs in-memory vs CDN for our API responses
+/brainstorm auth: next-auth vs Clerk vs custom JWT for our SaaS app
+/brainstorm state management: Zustand vs Redux vs TanStack Query
+/brainstorm monolith vs microservices for our current team size
+```

package/.agent/workflows/changelog.md

@@ -1,112 +1,140 @@
----
-description: Auto-generate changelogs from git history. Categorizes commits by type (feat/fix/chore/breaking) and follows Keep a Changelog format. Requires conventional commit messages for accurate categorization.
----
-
-# /changelog — Git History to Changelog
-
-$ARGUMENTS
-
----
-
-## When to Use /changelog
-
-|Use `/changelog` when...||
-|:---|:---|
-|Preparing a release|Generate for specific version range|
-|Documenting recent changes|Generate since last tag|
-|Onboarding someone to codebase history|Generate entire history|
-
----
-
-## Commit Convention (Required for Accuracy)
-
-```
-Format: <type>(<scope>): <description>
-
-Types:
-  feat:     New functionality (appears in "Added")
-  fix:      Bug fix (appears in "Fixed")
-  chore:    Maintenance, deps (appears in "Changed")
-  docs:     Documentation only
-  perf:     Performance improvement (appears in "Changed")
-  refactor: Internal restructuring (appears in "Changed")
-  test:     Test-only changes
-  BREAKING CHANGE: Footer or body annotation (appears in "Breaking Changes")
-```
-
----
-
-## Git Log Commands
-
-```bash
-# Since last tag
-git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
-
-# Since a specific date
-git log --since="2026-01-01" --oneline --no-merges
-
-# Since specific commit
-git log abc123def..HEAD --oneline --no-merges
-
-# With full commit message (for BREAKING CHANGE in body)
-git log $(git describe --tags --abbrev=0)..HEAD --format="%H %s%n%b"
-```
-
----
-
-## Output Format (Keep a Changelog)
-
-```markdown
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [Unreleased]
-
-## [1.2.0] — 2026-04-02
-
-### Breaking Changes
-- **auth**: JWT token format changed — clients must re-authenticate ([abc123](link))
-
-### Added
-- User notification system with email and in-app alerts ([def456](link))
-- Pagination on /api/users endpoint with meta.total in response ([ghi789](link))
-
-### Fixed
-- JWT verify no longer accepts 'none' algorithm ([jkl012](link))
-- Checkout form no longer loses data on page refresh ([mno345](link))
-
-### Changed
-- Upgraded Prisma 5 to 6 — findOne calls migrated to findUnique ([pqr678](link))
-- Bundle size reduced 64% via dynamic import for chart library ([stu901](link))
-
-## [1.1.0] — 2026-03-15
-[...]
-
-[Unreleased]: https://github.com/user/repo/compare/v1.2.0...HEAD
-[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
-```
-
----
-
-## Semver Decision Guide
-
-```
-MAJOR (1.0.0 → 2.0.0): Any BREAKING CHANGE
-MINOR (1.0.0 → 1.1.0): New features, backward-compatible (feat:)  
-PATCH (1.0.0 → 1.0.1): Bug fixes only (fix:)
-```
-
----
-
-## Usage Examples
-
-```
-/changelog since last release tag
-/changelog for version 1.2.0 including all commits since v1.1.0
-/changelog since 2026-01-01
-/changelog what changed in the authentication module this month
-```
+---
+description: Auto-generate changelogs from git history. Categorizes commits by type (feat/fix/chore/breaking) and follows Keep a Changelog format. Requires conventional commit messages for accurate categorization.
+required-skills: github-operations
+---
+
+# /changelog — Git History to Changelog
+
+$ARGUMENTS
+
+---
+
+## $CONTEXT_REQUIRED
+
+```
+Read BEFORE generating changelog:
+□ git log --oneline -20       → Verify commit message format
+□ package.json                → Identify current version
+□ CHANGELOG.md (if exists)    → Understand existing format/history
+```
+
+---
+
+## When to Use /changelog
+
+| Use `/changelog` when...               |                                     |
+| :------------------------------------- | :---------------------------------- |
+| Preparing a release                    | Generate for specific version range |
+| Documenting recent changes             | Generate since last tag             |
+| Onboarding someone to codebase history | Generate entire history             |
+
+---
+
+## Commit Convention (Required for Accuracy)
+
+```
+Format: <type>(<scope>): <description>
+
+Types:
+  feat:     New functionality (appears in "Added")
+  fix:      Bug fix (appears in "Fixed")
+  chore:    Maintenance, deps (appears in "Changed")
+  docs:     Documentation only
+  perf:     Performance improvement (appears in "Changed")
+  refactor: Internal restructuring (appears in "Changed")
+  test:     Test-only changes
+  BREAKING CHANGE: Footer or body annotation (appears in "Breaking Changes")
+```
+
+---
+
+## Git Log Commands
+
+```bash
+# Since last tag
+git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
+
+# Since a specific date
+git log --since="2026-01-01" --oneline --no-merges
+
+# Since specific commit
+git log abc123def..HEAD --oneline --no-merges
+
+# With full commit message (for BREAKING CHANGE in body)
+git log $(git describe --tags --abbrev=0)..HEAD --format="%H %s%n%b"
+```
+
+---
+
+## Output Format (Keep a Changelog)
+
+```markdown
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [1.2.0] — 2026-04-02
+
+### Breaking Changes
+
+- **auth**: JWT token format changed — clients must re-authenticate ([abc123](link))
+
+### Added
+
+- User notification system with email and in-app alerts ([def456](link))
+- Pagination on /api/users endpoint with meta.total in response ([ghi789](link))
+
+### Fixed
+
+- JWT verify no longer accepts 'none' algorithm ([jkl012](link))
+- Checkout form no longer loses data on page refresh ([mno345](link))
+
+### Changed
+
+- Upgraded Prisma 5 to 6 — findOne calls migrated to findUnique ([pqr678](link))
+- Bundle size reduced 64% via dynamic import for chart library ([stu901](link))
+
+## [1.1.0] — 2026-03-15
+
+[...]
+
+[Unreleased]: https://github.com/user/repo/compare/v1.2.0...HEAD
+[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
+```
+
+---
+
+## Semver Decision Guide
+
+```
+MAJOR (1.0.0 → 2.0.0): Any BREAKING CHANGE
+MINOR (1.0.0 → 1.1.0): New features, backward-compatible (feat:)
+PATCH (1.0.0 → 1.0.1): Bug fixes only (fix:)
+```
+
+---
+
+## Usage Examples
+
+```
+/changelog since last release tag
+/changelog for version 1.2.0 including all commits since v1.1.0
+/changelog since 2026-01-01
+/changelog what changed in the authentication module this month
+```
+
+---
+
+## After /changelog — Next Steps
+
+| Outcome                             | Next Command                        |
+| :---------------------------------- | :---------------------------------- |
+| Changelog updated, ready to release | → `/deploy` or tag version          |
+| Need to summarize for non-technical | → Request PR description generation |
+
+---