estimate

Name: estimate
Author: tranhieutt

69stars41forks

How to install estimate?

tranhieutt/software_development_department/estimate

$npx -y skills add tranhieutt/software_development_department --skill estimate

Installs into the current project.

Summary

Produces time and complexity estimates for features, tasks, or sprints using story points, t-shirt sizing, or day estimates. Use when the user asks for an estimate, wants to size a feature, or mentions estimation or planning poker.

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Read the task description from the argument. If the description is too
4	vague to estimate meaningfully, ask for clarification before proceeding.
5
6	2. Read CLAUDE.md for project context: tech stack, coding standards,
7	architectural patterns, and any estimation guidelines.
8
9	3. Read relevant design documents from `design/docs/` if the task relates
10	to a documented feature or system.
11
12	4. Scan the codebase to understand the systems affected by this task:
13	- Identify files and modules that would need to change
14	- Assess the complexity of those files (size, dependency count, cyclomatic
15	complexity)
16	- Identify integration points with other systems
17	- Check for existing test coverage in the affected areas
18
19	5. Read past sprint data from `production/sprints/` if available:
20	- Look for similar completed tasks and their actual effort
21	- Calculate historical velocity (planned vs actual)
22	- Identify any estimation bias patterns (consistently over or under)
23
24	6. Analyze the following factors:
25
26	Code Complexity:
27	- Lines of code in affected files
28	- Number of dependencies and coupling level
29	- Whether this touches core/engine code vs leaf/feature code
30	- Whether existing patterns can be followed or new patterns are needed
31
32	Scope:
33	- Number of systems touched
34	- New code vs modification of existing code
35	- Amount of new test coverage required
36	- Data migration or configuration changes needed
37
38	Risk:
39	- New technology or unfamiliar libraries
40	- Unclear or ambiguous requirements
41	- Dependencies on unfinished work
42	- Cross-system integration complexity
43	- Performance sensitivity
44
45	7. Generate the estimate:
46
47	```markdown
48	## Task Estimate: [Task Name]
49	Generated: [Date]
50
51	### Task Description
52	[Restate the task clearly in 1-2 sentences]
53
54	### Complexity Assessment
55
56	\| Factor \| Assessment \| Notes \|
57	\|--------\|-----------\|-------\|
58	\| Systems affected \| [List] \| [Core, business, UI, etc.] \|
59	\| Files likely modified \| [Count] \| [Key files listed below] \|
60	\| New code vs modification \| [Ratio, e.g., 70% new / 30% modification] \| \|
61	\| Integration points \| [Count] \| [Which systems interact] \|
62	\| Test coverage needed \| [Low / Medium / High] \| [Unit, integration, manual] \|
63	\| Existing patterns available \| [Yes / Partial / No] \| [Can follow existing code or new ground] \|
64
65	Key files likely affected:
66	- `[path/to/file1]` -- [what changes here]
67	- `[path/to/file2]` -- [what changes here]
68	- `[path/to/file3]` -- [what changes here]
69
70	### Effort Estimate
71
72	\| Scenario \| Days \| Assumption \|
73	\|----------\|------\|------------\|
74	\| Optimistic \| [X] \| Everything goes right, no surprises, requirements are clear \|
75	\| Expected \| [Y] \| Normal pace, minor issues, one round of review feedback \|
76	\| Pessimistic \| [Z] \| Significant unknowns surface, blocked for a day, requirements change \|
77
78	Recommended budget: [Y days]
79
80	[If historical data is available: "Based on [N] similar tasks that averaged
81	[X] days actual vs [Y] days estimated, a [correction factor] adjustment has
82	been applied."]
83
84	### Confidence: [High / Medium / Low]
85
86	High -- Clear requirements, familiar systems, follows existing patterns,
87	similar tasks completed before.
88
89	Medium -- Some unknowns, touches moderately complex systems, partial
90	precedent from previous work.
91
92	Low -- Significant unknowns, new technology, unclear requirements, or
93	cross-cutting concerns across many systems.
94
95	[Explain which factors drive the confidence level for this specific task.]
96
97	### Risk Factors
98
99	\| Risk \| Likelihood \| Impact \| Mitigation \|
100	\|------\|-----------\|--------\|------------\|
101	\| [Specific risk] \| [High/Med/Low] \| [Days added if realized] \| [How to reduce] \|
102	\| [Another risk] \| [Likelihood] \| [Impact] \| [Mitigation] \|
103
104	### Dependencies
105
106	\| Dependency \| Status \| Impact if Delayed \|
107	\|-----------\|--------\|-------------------\|
108	\| [What must be done first] \| [Done / In Progress / Not Started] \| [How it affects this task] \|
109
110	### Suggested Breakdown
111
112	\| # \| Sub-task \| Estimate \| Notes \|
113	\|---\|----------\|----------\|-------\|
114	\| 1 \| [Research / spike] \| [X days] \| [If unknowns need investigation first] \|
115	\| 2 \| [Core implementation] \| [X days] \| [The main work] \|
116	\| 3 \| [Integration with system X] \| [X days] \| [Connecting to existing code] \|
117	\| 4 \| [Testing and validation] \| [X days] \| [Writing tests, manual verification] \|
118	\| 5 \| [Code review and iteration] \| [X days] \| [Review feedback, fixes] \|
119	\| \| Total \| [Y days] \| \|
120
121	### Historical Compariso

People who liked this also viewed

6 picks

Type

estimate

69stars41forks

View on GitHub

How to install estimate?

tranhieutt/software_development_department/estimate

$npx -y skills add tranhieutt/software_development_department --skill estimate

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	When this skill is invoked:
2
3	1. Read the task description from the argument. If the description is too
4	vague to estimate meaningfully, ask for clarification before proceeding.
5
6	2. Read CLAUDE.md for project context: tech stack, coding standards,
7	architectural patterns, and any estimation guidelines.
8
9	3. Read relevant design documents from `design/docs/` if the task relates
10	to a documented feature or system.
11
12	4. Scan the codebase to understand the systems affected by this task:
13	- Identify files and modules that would need to change
14	- Assess the complexity of those files (size, dependency count, cyclomatic
15	complexity)
16	- Identify integration points with other systems
17	- Check for existing test coverage in the affected areas
18
19	5. Read past sprint data from `production/sprints/` if available:
20	- Look for similar completed tasks and their actual effort
21	- Calculate historical velocity (planned vs actual)
22	- Identify any estimation bias patterns (consistently over or under)
23
24	6. Analyze the following factors:
25
26	Code Complexity:
27	- Lines of code in affected files
28	- Number of dependencies and coupling level
29	- Whether this touches core/engine code vs leaf/feature code
30	- Whether existing patterns can be followed or new patterns are needed
31
32	Scope:
33	- Number of systems touched
34	- New code vs modification of existing code
35	- Amount of new test coverage required
36	- Data migration or configuration changes needed
37
38	Risk:
39	- New technology or unfamiliar libraries
40	- Unclear or ambiguous requirements
41	- Dependencies on unfinished work
42	- Cross-system integration complexity
43	- Performance sensitivity
44
45	7. Generate the estimate:
46
47	```markdown
48	## Task Estimate: [Task Name]
49	Generated: [Date]
50
51	### Task Description
52	[Restate the task clearly in 1-2 sentences]
53
54	### Complexity Assessment
55
56	\| Factor \| Assessment \| Notes \|
57	\|--------\|-----------\|-------\|
58	\| Systems affected \| [List] \| [Core, business, UI, etc.] \|
59	\| Files likely modified \| [Count] \| [Key files listed below] \|
60	\| New code vs modification \| [Ratio, e.g., 70% new / 30% modification] \| \|
61	\| Integration points \| [Count] \| [Which systems interact] \|
62	\| Test coverage needed \| [Low / Medium / High] \| [Unit, integration, manual] \|
63	\| Existing patterns available \| [Yes / Partial / No] \| [Can follow existing code or new ground] \|
64
65	Key files likely affected:
66	- `[path/to/file1]` -- [what changes here]
67	- `[path/to/file2]` -- [what changes here]
68	- `[path/to/file3]` -- [what changes here]
69
70	### Effort Estimate
71
72	\| Scenario \| Days \| Assumption \|
73	\|----------\|------\|------------\|
74	\| Optimistic \| [X] \| Everything goes right, no surprises, requirements are clear \|
75	\| Expected \| [Y] \| Normal pace, minor issues, one round of review feedback \|
76	\| Pessimistic \| [Z] \| Significant unknowns surface, blocked for a day, requirements change \|
77
78	Recommended budget: [Y days]
79
80	[If historical data is available: "Based on [N] similar tasks that averaged
81	[X] days actual vs [Y] days estimated, a [correction factor] adjustment has
82	been applied."]
83
84	### Confidence: [High / Medium / Low]
85
86	High -- Clear requirements, familiar systems, follows existing patterns,
87	similar tasks completed before.
88
89	Medium -- Some unknowns, touches moderately complex systems, partial
90	precedent from previous work.
91
92	Low -- Significant unknowns, new technology, unclear requirements, or
93	cross-cutting concerns across many systems.
94
95	[Explain which factors drive the confidence level for this specific task.]
96
97	### Risk Factors
98
99	\| Risk \| Likelihood \| Impact \| Mitigation \|
100	\|------\|-----------\|--------\|------------\|
101	\| [Specific risk] \| [High/Med/Low] \| [Days added if realized] \| [How to reduce] \|
102	\| [Another risk] \| [Likelihood] \| [Impact] \| [Mitigation] \|
103
104	### Dependencies
105
106	\| Dependency \| Status \| Impact if Delayed \|
107	\|-----------\|--------\|-------------------\|
108	\| [What must be done first] \| [Done / In Progress / Not Started] \| [How it affects this task] \|
109
110	### Suggested Breakdown
111
112	\| # \| Sub-task \| Estimate \| Notes \|
113	\|---\|----------\|----------\|-------\|
114	\| 1 \| [Research / spike] \| [X days] \| [If unknowns need investigation first] \|
115	\| 2 \| [Core implementation] \| [X days] \| [The main work] \|
116	\| 3 \| [Integration with system X] \| [X days] \| [Connecting to existing code] \|
117	\| 4 \| [Testing and validation] \| [X days] \| [Writing tests, manual verification] \|
118	\| 5 \| [Code review and iteration] \| [X days] \| [Review feedback, fixes] \|
119	\| \| Total \| [Y days] \| \|
120
121	### Historical Compariso

People who liked this also viewed

6 picks

Type