← Project SimpleCONTENT HISTORY

Update to Project Simple

Snapshot Nov 16, 2026 · 18:15 UTC · version 1.0.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Project Simple and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Plan, fill, check and start a team's sprint in Project Simple. Use when the user wants to create or fill a sprint, asks whether a sprint can start, asks about capacity or who is on time off, or wants to start or halt a sprint.",
  "included_files": [],
  "name": "sprint-planning",
  "skill_md_contents": "---\nname: sprint-planning\ndescription: Plan, fill, check and start a team's sprint in Project Simple. Use when the user wants to create or fill a sprint, asks whether a sprint can start, asks about capacity or who is on time off, or wants to start or halt a sprint.\n---\n\nSprints belong to a team, not to a project, and are numbered rather than named. A team runs one\nsprint at a time. Follow the `project-simple-rules` skill for references, links and confirmations.\n\n## See where the team stands\n\n1. `get_current_sprint` for the running sprint of each team the user is on; `list_sprints` for\n   planned and past ones; `get_sprint` for one sprint's items and dates.\n2. Report items with their status and the link that opens them in Project Simple.\n\n## Plan and fill a sprint\n\n1. If there is no planned sprint, `create_sprint` for the team. Keep the team's usual cycle and\n   WIP defaults unless the user asks for different ones.\n2. Find candidate work with `search_items` using `scope=BACKLOG` and `onlyOpen`, in backlog order.\n3. Show the user the items you intend to move and wait for a yes. Then `move_items_to_sprint`\n   in one call for several items, or `move_item_to_sprint` for one.\n4. Check capacity before over-filling: `get_sprint_capacity` for an existing sprint, or\n   `estimate_sprint_capacity` for dates that have no sprint yet. Capacity comes from the team's\n   engineers, the working days in the sprint, the time off booked for them and the sprint's\n   utilization ratio.\n\n## Time off\n\n- `list_time_off` and `get_time_off_summary` show who is away and when.\n- `schedule_time_off` books time off and changes the capacity of every sprint those dates fall\n  in. Say so when you report it. `update_time_off` and `cancel_time_off` adjust a booking.\n\n## Start a sprint\n\n1. Call `get_sprint_readiness` first. A sprint will not start until every item in it is broken\n   down into tasks and estimated, and no other sprint of that team is running.\n2. If it is not ready, list exactly what is in the way: which items lack tasks or estimates, or\n   which sprint is still running. Offer to add tasks with `add_item_tasks` or estimates with\n   `update_item`. Do not call `start_sprint` until readiness passes.\n3. When it is ready, confirm with the user, then `start_sprint`.\n\n## Halt a sprint\n\n`halt_sprint` ends the sprint, carries unfinished work over and cannot be undone. Explain that,\nget an explicit yes, and only then call it. Report what was carried over.\n\n## Estimating with the team\n\n`invite_to_story_poker` asks a team to vote on an item's story points. Each invitee gets a TODO,\nvotes stay hidden until the session completes, and inviting again replaces an open session, so\ncheck `get_story_poker_history` and confirm before re-inviting. `submit_story_poker_vote` records\nthe signed-in user's own vote.\n"
}

SHA-256 of public snapshot: 6aa5ccfddf5edd6226b165fba6f01d3890d621ad60297aa461724cf3c0849d44