@dabble/linear-cli 1.0.2 → 1.0.3

package/claude/commands/done.md

@@ -15,11 +15,11 @@ Help the developer wrap up their work on the current Linear issue.
 2. **Summarize the work** by checking:
    - `git log --oneline <base>..HEAD` to see commits
    - `git diff --stat <base>..HEAD` to see files changed
-3. **Ask what they want to do** using AskUserQuestion:
-   - Close the issue in Linear
-   - Create a PR first
-   - Add final notes to the issue
-   - Just clean up (worktree only)
+3. **Ask what they want to do:**
+   - Create PR and close
+   - Close issue (no PR)
+   - Add notes and close
+   - Just clean up (keep issue open)
 
 ## After Selection
 
@@ -50,11 +50,7 @@ You've made 3 commits on ISSUE-12: Add caching layer
 - src/cache.ts (new file, 45 lines)
 - src/api.ts (modified, +12 -3)
 
-What would you like to do?
-1. Create PR and close issue
-2. Close issue (no PR)
-3. Add notes and close
-4. Just clean up worktree (don't close)
+[Presents options above]
 ```
 
 ## Notes

package/claude/commands/next.md

@@ -21,47 +21,11 @@ Skip straight to starting work on that issue (see "Starting Work on an Issue" be
 
 ### Presenting Options
 
-Always present a numbered list with these rules:
-- Show up to **5 issues maximum** (yours are already sorted first by the CLI)
-- If more than 5 issues exist, note how many more after the list
-- **Always** include "Product planning" as the final option
-
-### Format
-
-```
-Here's what's ready to work on:
-
-1. ISSUE-5: Add caching layer [Backlog] (assigned to you)
-2. ISSUE-8: Fix login timeout [Backlog]
-3. ISSUE-12: Update API docs [Backlog]
-4. ISSUE-18: Do Something Else [Backlog]
-5. ISSUE-29: Another thing [Backlog]
-   ... and 7 more unblocked issues
-6. Product planning - brainstorm features, review backlog, plan next phase
-
-Which would you like to work on?
-```
-
-### If NO unblocked issues:
-
-```
-No unblocked issues at the moment.
-
-1. Product planning - brainstorm features, review backlog, plan next phase
-
-Would you like to work on product planning?
-```
-
-### If exactly ONE issue:
-
-```
-There's one issue ready to work on:
-
-1. ISSUE-5: Add caching layer [Backlog] (assigned to you)
-2. Product planning - brainstorm features, review backlog, plan next phase
-
-Which would you like?
-```
+Present interactive options:
+- Up to **3 issues** (CLI already sorts yours first)
+- **Always** include "Product planning" as an option
+- If >3 issues, note how many more
+- User can always type a specific issue ID
 
 ## Starting Work on an Issue
 
@@ -70,25 +34,19 @@ When the user selects an issue (or provides one directly via `/next ISSUE-12`):
 1. Run `linear issue start <id>` to assign and set In Progress
 2. Run `linear branch <id>` to create a git branch
 3. Run `linear issue show <id>` to display full context
-4. **Enter plan mode** using the EnterPlanMode tool
-
-This ensures every issue starts with a proper implementation plan before writing code.
+4. **Enter plan mode** to explore the codebase and design an implementation approach
 
 ## If they choose "Product planning"
 
-Start a planning session by asking:
-
-"What would you like to focus on?"
-- Review and prioritize the backlog
+Ask what they want to focus on:
+- Review and prioritize backlog
 - Brainstorm new features
 - Plan the next phase
-- Something specific
 
-Then follow the product-planning skill guidelines to facilitate the session.
+Then follow the product-planning skill guidelines.
 
 ## Notes
 
 - Always use long flags (--unblocked, not -u) for clarity
 - The CLI already sorts your assigned issues first
-- If presenting options, use the AskUserQuestion tool for a clean interface
 - The "Product planning" option ensures there's always something productive to do

package/claude/commands/standup.md

@@ -24,10 +24,10 @@ Run `linear standup` to get:
 ## After Running
 
 1. Present the output from `linear standup` to the user
-2. Offer to help with:
-   - Drafting a standup message for Slack/Teams
-   - Identifying what to work on next (suggest `/next`)
-   - Resolving any blockers
+2. Ask what they want to do next:
+   - Draft standup message (for Slack/Teams)
+   - Find next issue (run /next)
+   - Resolve blockers
 
 ## Example Flow
 
@@ -52,7 +52,7 @@ Here's your standup summary:
 - 4 commits on beautiful-tech
 - PR #42 merged: ISSUE-5: Add caching layer
 
-Would you like me to help draft a standup message, or shall we look at what to work on next?
+[Presents options above]
 ```
 
 ## Notes

package/claude/skills/{product-planning.md → product-planning/SKILL.md}

@@ -1,7 +1,6 @@
 ---
 name: product-planning
 description: Facilitate product thinking and structure work in Linear.
-allowed-tools: Bash(linear:*), Bash(curl:*), "WebFetch(domain:*)", "WebSearch"
 ---
 
 # Product Planning
@@ -28,8 +27,6 @@ linear issues --open  # Active work
 
 Read `product.md` if it exists—contains product vision, brand, tech decisions, prior planning context.
 
-Offer web research when exploring new territory (market landscape, competitors, technical feasibility).
-
 ## Process
 
 ### 1. Explore the Problem
@@ -41,6 +38,8 @@ Before solutions:
 - What constraints? (time, tech, dependencies)
 - What's uncertain or risky?
 
+Proactively search the web when exploring unfamiliar territory (competitors, market, technical approaches).
+
 ### 2. Design the Solution
 
 - What approaches exist? Tradeoffs?
@@ -51,6 +50,8 @@ Before solutions:
 
 Cut scope aggressively—except for core/differentiating features where polish and detail set you apart.
 
+For technical work, explore the existing codebase first to understand patterns and architecture.
+
 ### 3. Structure the Work
 
 **Sizing:** XS/S/M = single issue, < 1 day. L/XL = needs breakdown.
@@ -99,6 +100,8 @@ Create the file if it doesn't exist. Keep it concise.
 
 ## Session Summary
 
+Track progress throughout the session, then summarize:
+
 1. **Created** - Issues/milestones with IDs
 2. **Decided** - Key decisions and rationale
 3. **Deferred** - What we cut (and why)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dabble/linear-cli",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Linear CLI with unblocked issue filtering, built for AI-assisted development",
   "type": "module",
   "bin": {