Repository navigation
0.3.0
SpecsGraph SDLC P1 is live: the MCP server has 35 tools (12 read, 23 write). task_submitReady is gone; thread_ask, proposal_plan and proposal_assign are new, and spec_apply takes plan.
Changed
/specsgraph:setupwrites the section the web app's Connect an agent panel shows: readworkstream:WS-nwhile the spec is in flight, ask withthread_askinstead of guessing, people mark a task Ready and publish it and the landing marks it done, cite tracker keys such as KAN-43. It no longer namestask_submitReady.- Product, engineer and brownfield: stage work for a task into a plan (
spec_applywithplan,proposal_plan,proposal_assign); ask the team withthread_ask(options,blocking,askTeam) and collect answers withthread_list(kind,answeredSince); change requests hold an accept until the artefact is staged again; only a person reopens a question or a change request, and a conflict thread never reopens. Closing steps say Ready is a person's act and the task moves to Done when its publication lands. - Director: orientation checks a workstream for questions still waiting on people.
- README: plans, and no tool marks a Task Ready or answers a question.
scripts/tools.jsonregenerated from the P1 tool registry.