Skills task-estimation
๐Ÿ“ฆ

task-estimation

Content revision r1 Safe โš™๏ธ External commands๐ŸŒ Network access

Estimate Agile Tasks With Story Points

Teams need consistent estimates for sprint planning and roadmaps. This skill guides story points, planning poker, sizing, risks, and task breakdowns.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "task-estimation" from https://skillstore.io/skills/supercent-io-task-estimation.md and its manifest at https://skillstore.io/api/skills/supercent-io-task-estimation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "task-estimation". Task: Add profile photo upload with size validation and existing cloud storage.

Expected outcome:

Estimate: 5 story points, medium size, and 1-2 days. Main risks are file validation, image processing, and permission checks.

Using "task-estimation". Epic: Add subscription payments for web and mobile users.

Expected outcome:

Recommendation: split the epic. Create separate stories for checkout, account status, webhook handling, refunds, mobile purchase flow, and testing.

Using "task-estimation". Roadmap item: Build an admin analytics dashboard with unknown reporting requirements.

Expected outcome:

Estimate: high uncertainty. Run discovery first, define required metrics, then estimate charts, export needs, permissions, and performance work separately.

Security Audit

Safe
v4 โ€ข 7/7/2026 Open versioned report

All external command findings are false positives from Markdown code fences and inline tags. The URL findings are reference links only, with no prompt injection or exfiltration intent found.

2
Files scanned
236
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/supercent-io-task-estimation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/supercent-io-task-estimation/security.svg)](https://skillstore.io/skills/supercent-io-task-estimation?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/supercent-io-task-estimation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/supercent-io-task-estimation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/supercent-io-task-estimation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

supercent-io. (2026). task-estimation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/supercent-io-task-estimation/audits/4

BibTeX citation

@techreport{supercent-io-supercent-io-task-estimation-2026, author = {supercent-io}, title = {task-estimation security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/supercent-io-task-estimation/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "task-estimation security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "supercent-io" date-released: "2026-07-07" url: "https://skillstore.io/skills/supercent-io-task-estimation/audits/4" identifiers: - type: other value: "skillstore:supercent-io-task-estimation:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
69
Community
83
Spec Compliance

What You Can Build

Plan a sprint backlog

Estimate candidate stories, compare effort, and choose a realistic sprint scope.

Shape a product roadmap

Turn feature ideas into rough sizes before sequencing quarterly work.

Review engineering risk

Adjust estimates for unknowns, dependencies, integration work, and testing needs.

Try These Prompts

Estimate a single task
Estimate this task with story points, t-shirt size, time range, risks, dependencies, and assumptions: [task details].
Prepare planning poker notes
Create planning poker notes for this story. Include questions, likely estimate range, risk factors, and reasons for high or low votes: [story].
Split a large epic
Break this epic into smaller estimable stories. For each story, include acceptance criteria, estimate, dependencies, and open questions: [epic].
Calibrate a roadmap estimate
Using this team velocity and backlog, estimate delivery ranges. Show confidence, sequencing risks, dependencies, and where estimates need discovery: [context].

Best Practices

  • Provide acceptance criteria before asking for an estimate.
  • Compare each task with similar completed work.
  • Separate high-risk unknowns into discovery tasks.

Avoid

  • Do not treat estimates as promises from individuals.
  • Do not estimate large epics without splitting them first.
  • Do not ignore team velocity, dependencies, or technical risk.

Frequently Asked Questions

Can this skill estimate both points and time?
Yes. It can provide story points, t-shirt sizes, and rough time ranges when enough context is available.
Does it replace team planning poker?
No. It helps prepare discussion, but final estimates should come from team consensus.
What information should I provide?
Provide the task goal, acceptance criteria, dependencies, risks, and any similar past work.
Can it estimate large epics?
It can identify large epics and suggest smaller stories before assigning final estimates.
Does it use project history automatically?
No. You need to provide velocity, past estimates, or delivery history if you want calibration.
Which tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

36e07d5e13068e5be64447e8f20b427cf2cbd21a

Maintenance freshness

7/18/2026

Usage

12 downloads ยท 119 views

File structure

๐Ÿ“„ SKILL.md

๐Ÿ“„ SKILL.toon