get-tbd 0.1.8

package/dist/docs/tbd-prime.md

@@ -0,0 +1,119 @@
+# tbd Workflow Context
+
+> **Context Recovery**: Run `tbd prime` after compaction, clear, or new session.
+> Hooks auto-call this in Claude Code when .tbd/ detected.
+
+# SESSION CLOSE PROTOCOL
+
+**CRITICAL**: Before saying “done” or “complete”, you MUST run this checklist:
+
+```
+[ ] 1. Stage and commit: git add + git commit
+[ ] 2. Push to remote: git push
+[ ] 3. Start CI watch (BLOCKS until done): gh pr checks <PR> --watch 2>&1
+[ ] 4. While CI runs: tbd close/update <id> for issues worked on
+[ ] 5. While CI runs: tbd sync
+[ ] 6. Return to step 3 and CONFIRM CI passed
+[ ] 7. If CI failed: fix, re-push, restart from step 3
+```
+
+## NON-NEGOTIABLE Requirements
+
+### CI: Wait for `--watch` to finish
+
+The `--watch` flag blocks until ALL checks complete.
+Do NOT see “passing” in early output and move on—wait for the **final summary** showing
+all checks passed.
+
+### tbd: Update issues and sync
+
+Every session must end with tbd in a clean state:
+- Close/update **every issue** you worked on
+- Run `tbd sync` and confirm it completed
+
+**Work is not done until pushed, CI passes, and tbd is synced.**
+
+## Core Rules
+
+- Track *all task work* not being done immediately as beads using `tbd` (discovered
+  work, future work, TODOs for the session, multi-session work)
+- When in doubt, prefer tbd for tracking tasks, bugs, and issues
+- Use `tbd create` for creating beads
+- Git workflow: update or close issues and run `tbd sync` at session end
+- If not given specific directions, check `tbd ready` for available work
+
+## Essential Commands
+
+### Finding Work
+
+- `tbd ready` - Show issues ready to work (no blockers)
+- `tbd list --status open` - All open issues
+- `tbd list --status in_progress` - Your active work
+- `tbd show <id>` - Detailed issue view with dependencies
+
+### Creating & Updating
+
+- `tbd create "title" --type task|bug|feature --priority 2` - New issue
+  - Priority: 0-4 (0=critical, 2=medium, 4=backlog).
+    Do NOT use "high"/"medium"/"low"
+- `tbd update <id> --status in_progress` - Claim work
+- `tbd update <id> --assignee username` - Assign to someone
+- `tbd close <id>` - Mark complete
+- `tbd close <id> --reason "explanation"` - Close with reason
+- **Tip**: When creating multiple issues, use parallel subagents for efficiency
+
+### Dependencies & Blocking
+
+- `tbd dep add <issue> <depends-on>` - Add dependency (issue depends on depends-on)
+- `tbd blocked` - Show all blocked issues
+- `tbd show <id>` - See what’s blocking/blocked by this issue
+
+### Sync & Collaboration
+
+- `tbd sync` - Sync with git remote (run at session end)
+- `tbd sync --status` - Check sync status without syncing
+
+Note: `tbd sync` handles all git operations for issues--no manual git push needed.
+
+### Project Health
+
+- `tbd stats` - Project statistics (open/closed/blocked counts)
+- `tbd doctor` - Check for issues (sync problems, missing hooks)
+
+## Common Workflows
+
+**Starting work:**
+
+```bash
+tbd ready                              # Find available work
+tbd show <id>                          # Review issue details
+tbd update <id> --status in_progress   # Claim it
+```
+
+**Completing work:**
+
+```bash
+tbd close <id>    # Mark complete
+tbd sync          # Push to remote
+```
+
+**Creating dependent work:**
+
+```bash
+tbd create "Implement feature X" --type feature
+tbd create "Write tests for X" --type task
+tbd dep add <tests-id> <feature-id>   # Tests depend on feature
+```
+
+## Setup Commands
+
+- `tbd setup --auto` - Non-interactive setup with smart defaults (for agents/scripts)
+- `tbd setup --interactive` - Interactive setup with prompts (for humans)
+- `tbd setup --from-beads` - Migrate from Beads to tbd
+
+## Quick Reference
+
+- **Priority levels**: 0=critical, 1=high, 2=medium (default), 3=low, 4=backlog
+- **Issue types**: task, bug, feature, epic
+- **Status values**: open, in_progress, closed
+- **JSON output**: Add `--json` to any command for machine-readable output

package/dist/docs/templates/architecture-doc.md

@@ -0,0 +1,117 @@
+---
+title: Architecture Doc Template
+description: Template for architecture documents
+---
+# Architecture: [Component/System Name]
+
+**Date:** YYYY-MM-DD **Author:** [Name] **Status:** Draft | In Review | Approved
+
+## Overview
+
+High-level description of what this architecture covers.
+
+## Goals and Non-Goals
+
+### Goals
+
+- Goal 1
+- Goal 2
+
+### Non-Goals
+
+- Non-goal 1
+- Non-goal 2
+
+## System Context
+
+How this component fits into the larger system.
+
+```
+[Diagram placeholder - describe the system context]
+```
+
+## Design
+
+### Components
+
+#### Component 1
+
+**Responsibility:** What this component does.
+
+**Interfaces:** How other components interact with it.
+
+#### Component 2
+
+**Responsibility:** What this component does.
+
+**Interfaces:** How other components interact with it.
+
+### Data Flow
+
+How data moves through the system.
+
+```
+[Diagram placeholder - describe the data flow]
+```
+
+### Data Model
+
+Key data structures and their relationships.
+
+### Interfaces
+
+#### External APIs
+
+| Endpoint | Method | Description |
+| --- | --- | --- |
+| `/api/example` | GET | Description |
+
+#### Internal Interfaces
+
+Key internal contracts between components.
+
+## Trade-offs and Alternatives
+
+### Decision 1: [Description]
+
+**Chosen approach:** What we decided.
+
+**Alternatives considered:**
+- Alternative A: Why rejected
+- Alternative B: Why rejected
+
+**Rationale:** Why we chose this approach.
+
+## Security Considerations
+
+- Authentication approach
+- Authorization model
+- Data protection measures
+
+## Operational Concerns
+
+### Monitoring
+
+What metrics and alerts are needed.
+
+### Logging
+
+What should be logged and at what level.
+
+### Deployment
+
+How this component is deployed.
+
+### Scaling
+
+How this component scales under load.
+
+## Open Questions
+
+- Question 1?
+- Question 2?
+
+## References
+
+- [Related doc](url)
+- [External reference](url)

package/dist/docs/templates/plan-spec.md

@@ -0,0 +1,69 @@
+---
+title: Plan Spec Template
+description: Template for feature planning specification documents
+---
+# Feature: [Feature Name]
+
+**Date:** YYYY-MM-DD **Author:** [Name] **Status:** Draft | In Review | Approved |
+Implemented
+
+## Overview
+
+Brief description of the feature and its purpose.
+
+## Goals
+
+- Goal 1
+- Goal 2
+
+## Non-Goals
+
+- What this feature explicitly does NOT cover
+
+## Background
+
+Context and motivation for this feature.
+
+## Design
+
+### Approach
+
+High-level approach to implementing this feature.
+
+### Components
+
+Key components or modules involved.
+
+### API Changes
+
+Any API additions or modifications.
+
+## Implementation Plan
+
+### Phase 1: [Name]
+
+- [ ] Task 1
+- [ ] Task 2
+
+### Phase 2: [Name] (if needed)
+
+- [ ] Task 3
+- [ ] Task 4
+
+## Testing Strategy
+
+How will this feature be tested?
+
+## Rollout Plan
+
+How will this feature be deployed?
+
+## Open Questions
+
+- Question 1?
+- Question 2?
+
+## References
+
+- Link to related docs
+- Link to related issues

package/dist/docs/templates/research-brief.md

@@ -0,0 +1,71 @@
+---
+title: Research Brief Template
+description: Template for research documents
+---
+# Research: [Topic]
+
+**Date:** YYYY-MM-DD **Author:** [Name] **Status:** In Progress | Complete
+
+## Overview
+
+What we’re researching and why.
+
+## Questions to Answer
+
+1. Question 1?
+2. Question 2?
+3. Question 3?
+
+## Scope
+
+What’s included and excluded from this research.
+
+## Findings
+
+### [Subtopic 1]
+
+Key findings here.
+
+### [Subtopic 2]
+
+Key findings here.
+
+## Options Considered
+
+### Option A: [Name]
+
+**Description:** What this option involves.
+
+**Pros:**
+- Pro 1
+- Pro 2
+
+**Cons:**
+- Con 1
+- Con 2
+
+### Option B: [Name]
+
+**Description:** What this option involves.
+
+**Pros:**
+- Pro 1
+- Pro 2
+
+**Cons:**
+- Con 1
+- Con 2
+
+## Recommendations
+
+Based on the findings, we recommend …
+
+## Next Steps
+
+- [ ] Action item 1
+- [ ] Action item 2
+
+## References
+
+- [Link 1](url)
+- [Link 2](url)