@we-scrum/cli 6.8.3 → 6.9.3

package/README.md

@@ -1,6 +1,6 @@
 # @we-scrum/cli
 
-Command-line tool and MCP server for the [we-scrum](https://github.com/BUONJG/we-scrum) application.
+Command-line tool for the [we-scrum](https://github.com/BUONJG/we-scrum) application.
 
 ## Installation
 
@@ -28,35 +28,49 @@ we-scrum use-project --projectId <id>   # Set project directly
 
 The selected project is persisted in `~/.we-scrum.json` and used by all subsequent commands.
 
-### MCP server
+### Development policies
 
-Start the we-scrum MCP server over stdio transport:
+```bash
+we-scrum synchronize-development-policies   # Sync development guidelines from we-scrum into the project
+```
+
+### Story analysis
+
+```bash
+we-scrum get-story-description --identificationNumber <id>   # Get the description of a story
+we-scrum get-story-analysis --identificationNumber <id>      # Get the analysis DSL for a story
+```
+
+### Story development
+
+```bash
+we-scrum get-next-task --identificationNumber <id>
+```
+
+Gets the next pending task (status: ToDo) for a story, including its description, type template, section analysis, and the IDs needed to start or complete it.
+
+If the next task is paused by an automation breakpoint, this command stops and reports the pause instead of returning task details — see [Automation breakpoints](#automation-breakpoints) below.
 
 ```bash
-we-scrum mcp
-we-scrum mcp --projectId <id>   # Override the active project for this session
+we-scrum start-task --identificationNumber <id> --changeId <changeId>      # Mark a specific task as in progress
+we-scrum complete-task --identificationNumber <id> --changeId <changeId>   # Mark the current in-progress task as done
 ```
 
-## MCP integration
+### Automation breakpoints
 
-Add the following to your MCP client configuration (e.g. Claude Desktop):
+A developer can set a breakpoint on a change from the we-scrum web app to pause automated development at that point. When `get-next-task` hits a change with a breakpoint set, it halts and reports the pause instead of proceeding.
 
-```json
-{
-    "mcpServers": {
-        "we-scrum": {
-            "command": "we-scrum",
-            "args": ["mcp"]
-        }
-    }
-}
+```bash
+we-scrum remove-automation-breakpoint --automationBreakpointId <id>
 ```
 
-### Available tools
+Clears the breakpoint so development can resume. The id is included in the `get-next-task` output when a breakpoint is hit.
+
+### Iterations
 
-| Tool | Description |
-|------|-------------|
-| `get_next_task` | Get the next pending task (status: ToDo) for a story, including its description, type template, section analysis, and the IDs needed to start or complete it. |
+```bash
+we-scrum update-iteration --name <name> [--capacity <capacity>] [--comment <comment>] [--startDate <date>] [--endDate <date>]
+```
 
 ## Requirements