From 5e5525a7d6afcbd569c7cc7602ba95d93d6402d5 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 24 Feb 2026 11:23:58 +0000 Subject: [PATCH] Noting that mcp calls are better than direct file manipulation --- .story_kit/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.story_kit/README.md b/.story_kit/README.md index 362252d..b438fda 100644 --- a/.story_kit/README.md +++ b/.story_kit/README.md @@ -15,12 +15,11 @@ When you start a new session with this project: -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' ``` - This returns the full tool catalog (create stories, spawn agents, record tests, manage worktrees, etc.). Familiarize yourself with the available tools before proceeding. + This returns the full tool catalog (create stories, spawn agents, record tests, manage worktrees, etc.). Familiarize yourself with the available tools before proceeding. These tools allow you to directly manipulate the workflow and spawn subsidiary agents without manual file manipulation. 2. **Read Context:** Check `.story_kit/specs/00_CONTEXT.md` for high-level project goals. 3. **Read Stack:** Check `.story_kit/specs/tech/STACK.md` for technical constraints and patterns. 4. **Check Work Items:** Look at `.story_kit/work/1_upcoming/` and `.story_kit/work/2_current/` to see what work is pending. -**Why This Matters:** The `.mcp.json` file indicates that you have programmatic access to tools like `create_story`, `start_agent`, `list_agents`, `get_agent_output`, and more. These tools allow you to directly manipulate the workflow and spawn subsidiary agents without manual file manipulation. ---