- Home
- Skills
- Product Management
- Lanewright Sprint Planner: SRS to weekly plan and backlogs
Works with the AI Agents you already use
Lanewright Sprint Planner: SRS to weekly plan and backlogs
Turn an SRS into a Monday-to-Sunday sprint plan in Word and Markdown, with backlog files per sprint that Lanewright or scrum-kit read as they are. Capacity is never exceeded.
Free
Lanewright Sprint Planner: SRS to weekly plan and backlogs
Example session with this skill installed
Plan the sprints from docs/requirements/srs.md, starting 16 November 2026, in the Lanewright format.
- Read your context and instructions
- Compiled the lanewright sprint planner
Real output (2026-11-07): weekly-sprint-plan.md and .docx, plus eight backlog files. The skill wrote them in Indonesian, like the SRS; translated into English for this page. This is docs/sprints/sprint-01-backlog.md in full, in the Lanewright format that Lanewright reads as it is.
Sprint 01 backlog
Sprint goal: The Laravel skeleton runs on staging with green CI, and the catalogue API returns sample services
Period: 16 – 22 November 2026
| ID | Item | Region / module | Owner | SP | Acceptance criteria |
|---|---|---|---|---|---|
| OPS-S01-01 | Laravel skeleton, portal and api module structure, staging/main branches (days 1–2) | tooling | platform-tooling | 2 | Foundation; the Laravel app passes php artisan test; portal/, api/ and database/ directories match kit.json; staging branch created; README on running it locally |
| OPS-S01-02 | GitHub Actions CI: lint (Pint) and php artisan test on every pull request | tooling | platform-tooling | 3 | NFR-08: pull requests to staging/main run lint and tests; a pull request with failing tests cannot be merged |
| OPS-S01-03 | Staging environment, secrets handling, automatic deploy from staging | tooling | platform-tooling | 5 | Foundation (A-10); a merge into staging deploys automatically; no .env in the repository; secrets in GitHub Secrets; migrations run on deploy |
| BE-1-S01-01 | API conventions and contract: /api/v1, JSON response and error format, OpenAPI (days 1–2) | api | module-dev | 2 | Foundation; one documented format for success and errors; validation errors return HTTP 422 with the list of fields; OpenAPI in the repository |
| BE-1-S01-02 | Core schema and seeders: users, roles, units, categories, services | shared | shared-module-owner | 5 | Foundation (A-09); migrations go up and down cleanly; seeders: 4 roles, 1 super admin from an environment variable (no password in the repository), 2 units, 3 categories, 5 sample services |
| BE-1-S01-03 | Catalogue API: list, search, filter, service details | api | module-dev | 3 | F-01 AC1–AC3; F-02 AC1–AC3; data for F-03 AC1 and F-04 AC1; active services only |
| FE-1-S01-01 | Portal skeleton: responsive layout, navigation, Indonesian copy, API client | portal | module-dev | 5 | NFR-07; NFR-09 (target still to confirm, OQ-23); the API client uses the BE-1-S01-01 error format |
| FE-1-S01-02 | Basic UI components: forms, tables, file upload, error and success messages | portal | module-dev | 3 | Foundation; HTTP 422 errors show under the matching field; a sample page of the components |
Out of scope this sprint
- Catalogue and detail screens (FE-1-S02-01, FE-1-S02-02): sprint 2, because they need this sprint's catalogue API
- Role authorization and the authentication API (BE-1-S02-01, BE-1-S02-02): sprint 2
- HTTPS enforced on staging (OPS-S02-01): sprint 2
Dependencies and risks
- BE-1-S01-01, BE-1-S01-02 and FE-1-S01-01 need OPS-S01-01 (days 1–2). OPS finishes the skeleton on day 1.
- FE-1-S01-01 needs BE-1-S01-01 (days 1–2). The API contract is agreed on day 2.
- The staging server may not be ready yet (A-10). OPS asks for access on day 1; without it, a temporary staging runs on the team's own server and this goes into the review.
- OPS-S01-01 touches Laravel root files (
composer.json,config/,routes/,artisan) that no kit.json region covers. It is recorded undertooling(PA-07), and the platform owner decides their region before the sprint starts.
Next step: Lanewright Backlog Check, then run the sprint.
Connects securely to your tools. The creator never sees your data.
About this skill
Lanewright Sprint Planner reads docs/requirements/srs.md, interviews you briefly (at most two rounds, with defaults) about start date, deadline, team roles, capacity, holidays, milestones, product owner, scrum master and event times, and writes:
docs/sprints/weekly-sprint-plan.mdand a Word copy, with: introduction, Scrum framework and events, team and capacity, Definition of Ready and Done, a sprint map, one section per weekly sprint (goal, backlog table, total story points against capacity, risks and dependencies, the increment to demo), project risks, metrics, and templates for the events.- One backlog file per sprint,
docs/sprints/sprint-{nn}-backlog.md, in the exact format your workflow tool reads. It detects Lanewright or scrum-kit from.claude/kit.jsonand checks that regions and owners match.
Planning rules: items of 2 to 10 story points, foundations first, every item with an owner and testable acceptance criteria from the SRS, a sprint's total never above its capacity (overflow moves to a later sprint, never into a bigger one), holidays you could not confirm marked "to confirm". It never overwrites a backlog that already has items.
It also lists the Definition of Done items that probably do not apply to this project (for example no login means no authorization test), with a reason each. These are proposals only: Backlog Check asks a human to approve them.
Next step: Lanewright Backlog Check, then run the sprints with Lanewright or the free scrum-kit.
These four skills prepare the work. To run the sprints, use Lanewright (paid): https://www.agensi.io/r/HUZAIRSAPUTRA?to=/skills/lanewright-sprint-workflow-for-ai-coding-agent-teams or the free scrum-kit Claude Code plugin: https://github.com/huzairsaputra/scrum-kit. They work without either.
Why four skills, not one: https://github.com/huzairsaputra/lanewright-planning#why-four-skills-not-one
The four free skills on Agensi: Intake https://www.agensi.io/r/HUZAIRSAPUTRA?to=/skills/lanewright-intake-raw-project-input-to-cited-facts, SRS https://www.agensi.io/r/HUZAIRSAPUTRA?to=/skills/lanewright-srs-cited-requirements-in-word-and-markdown, Sprint Planner https://www.agensi.io/r/HUZAIRSAPUTRA?to=/skills/lanewright-sprint-planner-srs-to-weekly-plan-and-backlogs, Backlog Check https://www.agensi.io/r/HUZAIRSAPUTRA?to=/skills/lanewright-backlog-check-readiness-check-and-human-sign-off
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Product Management.
Estimates are proposals; national holidays are listed from the model's knowledge and marked "to confirm"; one team and one repository per plan.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 4 days ago
- Free with an Agensi account
- Software
Python 3.8+
Permissions
File Scopes