sprint-planning

Name: sprint-planning
Author: omnigentx

31stars13forks

How to install sprint-planning?

omnigentx/jarvis/sprint-planning

$npx -y skills add omnigentx/jarvis --skill sprint-planning

Installs into the current project.

Summary

Sprint planning guide. Use when PM needs to break down tasks, estimate effort, prioritize backlog for the next development cycle.

Files · 1

View on GitHub

SKILL.md

1	# SPRINT PLANNING
2
3	## Process
4
5	1. Review backlog: Read list of incomplete tasks/features
6	2. Estimate effort: Use T-shirt sizing (S/M/L/XL)
7	- S: < 30 min, 1 member
8	- M: 1-2 hours, 1-2 members
9	- L: 3-5 hours, 2-3 members
10	- XL: > 5 hours, must be split
11	3. Prioritize: MoSCoW method (Must/Should/Could/Won't)
12	4. Assign: Select needed members (see team-roster)
13	5. Output: Sprint plan on Confluence + Jira issues
14
15	## Backlog Creation (for Analysis projects)
16
17	When the team is doing analysis/evaluation, the backlog IS the deliverable:
18
19	1. Collect inputs from team members (BA gap analysis, SA architecture review, Dev code analysis)
20	2. Create Jira stories for each improvement item:
21	- Summary: `[IMPROVEMENT] <concise title>`
22	- Description: Problem statement, proposed solution, expected impact
23	- Priority: Must/Should/Could/Won't
24	- Estimate: S/M/L/XL
25	- Acceptance Criteria: Definition of Done
26	3. Create sprint: `jira_create_sprint(board_id, name)`, move prioritized items in
27	4. Publish sprint plan: `confluence_create_page` with full overview + priority rationale
28
29	## Sprint Plan Template
30
31	Publish to Confluence (NOT workspace MD file):
32
33	```markdown
34	# Sprint [N] Plan
35	## Goal: [Sprint objective]
36	## Duration: [Start date] → [End date]
37
38	\| # \| Task \| Priority \| Size \| Assigned \| Jira Key \| Status \|
39	\|---\|------\|----------\|------\|----------\|----------\|--------\|
40	\| 1 \| ... \| Must \| M \| Minh - Dev \| JAR-xx \| TODO \|
41	```
42
43	## Visualizing the sprint
44
45	When the sprint timeline or task dependencies need to be reviewed by stakeholders,
46	embed a Mermaid diagram alongside the table — the dashboard renders it inline.
47
48	Gantt for the timeline:
49
50	```mermaid
51	gantt
52	title Sprint [N] Timeline
53	dateFormat YYYY-MM-DD
54	section Must-have
55	Task A :a1, 2026-05-01, 2d
56	Task B :a2, after a1, 3d
57	section Should-have
58	Task C :b1, 2026-05-04, 2d
59	```
60
61	Flowchart when tasks have ordering / dependency:
62
63	```mermaid
64	flowchart LR
65	A[Backlog grooming] --> B[Estimate]
66	B --> C{Priority}
67	C -->\|Must\| D[Sprint commit]
68	C -->\|Could\| E[Backlog]
69	```
70
71	Use a diagram only when it adds clarity beyond the table — skip for tiny sprints.
72
73	<planning_rules>
74	1. XL tasks MUST be split into M or S tasks — no exceptions
75	2. Each sprint should have no more than 5-7 main tasks
76	3. Must-have tasks MUST have sufficient resources assigned
77	4. Every task needs a clear Definition of Done
78	5. Sprint plan MUST be on Confluence, individual tasks MUST be Jira issues
79	</planning_rules>

People who liked this also viewed

6 picks

Type

sprint-planning

31stars13forks

View on GitHub

How to install sprint-planning?

omnigentx/jarvis/sprint-planning

$npx -y skills add omnigentx/jarvis --skill sprint-planning

Installs into the current project.

Summary

Sprint planning guide. Use when PM needs to break down tasks, estimate effort, prioritize backlog for the next development cycle.

Files · 1

View on GitHub

SKILL.md

1	# SPRINT PLANNING
2
3	## Process
4
5	1. Review backlog: Read list of incomplete tasks/features
6	2. Estimate effort: Use T-shirt sizing (S/M/L/XL)
7	- S: < 30 min, 1 member
8	- M: 1-2 hours, 1-2 members
9	- L: 3-5 hours, 2-3 members
10	- XL: > 5 hours, must be split
11	3. Prioritize: MoSCoW method (Must/Should/Could/Won't)
12	4. Assign: Select needed members (see team-roster)
13	5. Output: Sprint plan on Confluence + Jira issues
14
15	## Backlog Creation (for Analysis projects)
16
17	When the team is doing analysis/evaluation, the backlog IS the deliverable:
18
19	1. Collect inputs from team members (BA gap analysis, SA architecture review, Dev code analysis)
20	2. Create Jira stories for each improvement item:
21	- Summary: `[IMPROVEMENT] <concise title>`
22	- Description: Problem statement, proposed solution, expected impact
23	- Priority: Must/Should/Could/Won't
24	- Estimate: S/M/L/XL
25	- Acceptance Criteria: Definition of Done
26	3. Create sprint: `jira_create_sprint(board_id, name)`, move prioritized items in
27	4. Publish sprint plan: `confluence_create_page` with full overview + priority rationale
28
29	## Sprint Plan Template
30
31	Publish to Confluence (NOT workspace MD file):
32
33	```markdown
34	# Sprint [N] Plan
35	## Goal: [Sprint objective]
36	## Duration: [Start date] → [End date]
37
38	\| # \| Task \| Priority \| Size \| Assigned \| Jira Key \| Status \|
39	\|---\|------\|----------\|------\|----------\|----------\|--------\|
40	\| 1 \| ... \| Must \| M \| Minh - Dev \| JAR-xx \| TODO \|
41	```
42
43	## Visualizing the sprint
44
45	When the sprint timeline or task dependencies need to be reviewed by stakeholders,
46	embed a Mermaid diagram alongside the table — the dashboard renders it inline.
47
48	Gantt for the timeline:
49
50	```mermaid
51	gantt
52	title Sprint [N] Timeline
53	dateFormat YYYY-MM-DD
54	section Must-have
55	Task A :a1, 2026-05-01, 2d
56	Task B :a2, after a1, 3d
57	section Should-have
58	Task C :b1, 2026-05-04, 2d
59	```
60
61	Flowchart when tasks have ordering / dependency:
62
63	```mermaid
64	flowchart LR
65	A[Backlog grooming] --> B[Estimate]
66	B --> C{Priority}
67	C -->\|Must\| D[Sprint commit]
68	C -->\|Could\| E[Backlog]
69	```
70
71	Use a diagram only when it adds clarity beyond the table — skip for tiny sprints.
72
73	<planning_rules>
74	1. XL tasks MUST be split into M or S tasks — no exceptions
75	2. Each sprint should have no more than 5-7 main tasks
76	3. Must-have tasks MUST have sufficient resources assigned
77	4. Every task needs a clear Definition of Done
78	5. Sprint plan MUST be on Confluence, individual tasks MUST be Jira issues
79	</planning_rules>

People who liked this also viewed

6 picks

Type