@anthropologies/claudestory 0.1.44 → 0.1.46

package/dist/cli.js

@@ -8358,7 +8358,7 @@ function getInstalledVersion() {
   }
 }
 function getRunningVersion() {
-  return "0.1.44";
+  return "0.1.46";
 }
 var init_version_check = __esm({
   "src/autonomous/version-check.ts"() {
@@ -10923,7 +10923,7 @@ var init_mcp = __esm({
     init_init();
     ENV_VAR2 = "CLAUDESTORY_PROJECT_ROOT";
     CONFIG_PATH2 = ".story/config.json";
-    version = "0.1.44";
+    version = "0.1.46";
     main().catch((err) => {
       process.stderr.write(`Fatal: ${err instanceof Error ? err.message : String(err)}
 `);
@@ -14354,7 +14354,7 @@ async function runCli() {
     registerSessionCommand: registerSessionCommand2,
     registerRepairCommand: registerRepairCommand2
   } = await Promise.resolve().then(() => (init_register(), register_exports));
-  const version2 = "0.1.44";
+  const version2 = "0.1.46";
   class HandledError extends Error {
     constructor() {
       super("HANDLED_ERROR");

package/dist/mcp.js

@@ -7816,7 +7816,7 @@ function getInstalledVersion() {
   }
 }
 function getRunningVersion() {
-  return "0.1.44";
+  return "0.1.46";
 }
 
 // src/autonomous/guide.ts
@@ -10055,7 +10055,7 @@ async function ensureGitignoreEntries(gitignorePath, entries) {
 // src/mcp/index.ts
 var ENV_VAR2 = "CLAUDESTORY_PROJECT_ROOT";
 var CONFIG_PATH2 = ".story/config.json";
-var version = "0.1.44";
+var version = "0.1.46";
 function tryDiscoverRoot() {
   const envRoot = process.env[ENV_VAR2];
   if (envRoot) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anthropologies/claudestory",
-  "version": "0.1.44",
+  "version": "0.1.46",
   "license": "UNLICENSED",
   "description": "Cross-session context persistence for AI coding projects. Tracks tickets, issues, roadmap, and handovers so every session builds on the last.",
   "keywords": [

package/src/skill/SKILL.md

@@ -81,18 +81,71 @@ After `claudestory_status` returns, check in order:
 
 ## Step 3: Present Summary
 
-After loading context, present a concise summary:
+After loading context, present a summary with two parts: a conversational intro (2-3 sentences catching the user up), then structured tables showing actionable data.
 
-- Project progress (X/Y tickets complete, current phase)
-- What changed since last snapshot (from recap)
-- What the last session accomplished (from handover)
-- Next ticket to work on
-- Any high-severity issues or blockers
-- Key process rules (from lessons digest)
+**Part 1: Conversational intro (2-3 sentences)**
 
-For collaborative sessions, `claudestory_recommend` provides context-aware suggestions mixing tickets and issues. For autonomous sessions, `claudestory_ticket_next` provides queue-based next ticket.
+Open with the project name and progress. Mention what the last session accomplished in one sentence. Note anything important (no git repo, open issues, blockers). Keep it brief -- the tables carry the detail.
 
-Then ask: **"What would you like to work on?"**
+**Part 2: Structured tables**
+
+**Ready to Work** -- call `claudestory_recommend` for context-aware suggestions, then show a table of unblocked tickets ready to be picked up:
+
+```
+## Ready to Work
+| Ticket | Title                              | Phase      |
+|--------|-----------------------------------|------------|
+| T-001  | Project setup                     | foundation |
+| T-011  | Rate agreement conditions schema  | foundation |
+| T-012  | Audit trail infrastructure        | foundation |
+```
+
+Show up to 5 unblocked tickets. If more exist, note "(+N more unblocked)".
+
+**Decisions Pending** (only if there are TBD items in CLAUDE.md or undecided tech choices from the brief):
+
+```
+## Decisions Pending
+- PDF generation: managed service vs pure-JS (affects T-030)
+- Background jobs: Inngest vs Trigger.dev vs Vercel Cron (affects T-001)
+```
+
+**Open Issues** (only if issues exist with status "open"):
+
+```
+## Open Issues
+| Issue    | Title                  | Severity |
+|----------|------------------------|----------|
+| ISS-001  | Auth token expiry bug  | high     |
+```
+
+**Key Rules** (from lessons digest -- only if lessons exist, keep to 2-3 most important):
+
+Show as a brief callout, not a full list. Example: "Rules: integer cents for money, billing engine is pure logic, TDD for billing."
+
+**First session guide (show only when handover count is 0 or 1):**
+
+```
+Tip: You can also use these modes anytime:
+  /story auto           I work through tickets autonomously -- plan, review, build, commit, loop
+  /story guided T-XXX   One ticket end-to-end with planning and code review
+  /story review T-XXX   Review code you already wrote
+```
+
+Show this once or twice, then never again.
+
+**Part 3: AskUserQuestion**
+
+End with `AskUserQuestion`:
+- question: "What would you like to do?"
+- header: "Next"
+- options:
+  - "Work on [first recommended ticket ID + title] (Recommended)" -- the top ticket from the Ready table
+  - "Something else" -- I'll ask what you have in mind
+  - "Autonomous mode" -- I'll work through tickets on my own
+- (Other always available for free-text input)
+
+Most users want the recommended ticket -- make that one tap.
 
 ## Session Lifecycle
 

package/src/skill/setup-flow.md

@@ -375,9 +375,9 @@ After the user approves the proposal structure, use `AskUserQuestion` for refine
 - question: "Want me to refine these before creating?"
 - header: "Depth"
 - options:
-  - "Create as-is" -- create tickets now with just titles
+  - "Yes, refine + get a second opinion (Recommended)" -- I'll refine, then have an independent reviewer check my work
   - "Yes, refine them" -- I'll add descriptions, figure out dependencies, and flag oversized tickets
-  - "Yes, refine + get a second opinion" -- I'll refine, then have an independent reviewer check my work
+  - "Create as-is" -- create tickets now with just titles
 
 If "Create as-is" and no brief exists: warn "Note: tickets will have titles only -- you can add descriptions later."
 
@@ -436,7 +436,7 @@ After refinement, run an independent review of the full proposal (phases, ticket
 - question: "Write project governance files?"
 - header: "Files"
 - options:
-  - "Write both" -- CLAUDE.md and RULES.md
+  - "Write both (Recommended)" -- CLAUDE.md and RULES.md
   - "CLAUDE.md only"
   - "RULES.md only"
   - "Skip" -- I'll write them manually
@@ -487,7 +487,12 @@ After creation completes:
 - Confirm what was created (e.g., "Created 5 phases, 18 tickets, 3 issues, CLAUDE.md, and RULES.md")
 - Check if `.gitignore` includes `.story/snapshots/` (warn if missing -- snapshots should not be committed)
 - Write an initial handover documenting the setup decisions. Explicitly capture which gates were answered and what was chosen: surface, characteristics, stack, system shape, execution model, deployment, data model, domain complexity, auth model, sensitive domain, AI pattern/provider/processing (if applicable), design source. This handover is the source of truth for decisions; CLAUDE.md is the project description.
-- Setup complete. Continue with **Step 2: Load Context** in SKILL.md (already in your context). Execute all 6 steps -- the project now has data to load.
+
+Present a brief completion message and tell the user how to start:
+
+"Your project is set up -- [X] phases, [Y] tickets, CLAUDE.md, and RULES.md created. Type **`/story`** at the start of any session to load context and see what to work on. Or type **`/story auto`** to let me work through the tickets autonomously."
+
+Keep it to 2-3 sentences. The system teaches itself through use -- `/story` loads context, shows status, and suggests next work. No need for a manual.
 
 ---