Use when estimating implementation effort from a requirement source such as text, Word documents, or slide decks, and producing a structured workday breakdown
Estimate project implementation effort from a requirement source (short text, Word doc, or PPTX) and output a structured workday-based breakdown with scope items, potential function requirements, implementation notes, integration/setup/deployment tasks, and buffers.
.docx, or .pptxDo not use this skill as a commitment contract; it is an estimation aid.
source_text (few sentences), orsource_file_path (.docx or .pptx)project_nameestimation_granularity: | | pagefeaturefunctionsource_text or source_file_path must be provided. If both or neither are given, stop and request clarification.source_file_path is provided, verify the file exists and has a supported extension (.docx or .pptx) before proceeding.estimation_granularity must be one of the three allowed values.tech_constraints: stack constraints or required frameworkteam_profile: choose from advanced-developer | senior-developer | mixed-team (default: senior-developer)non_functional_requirements: performance, security, compliance, localization, accessibilityconfidence_target: rough | normal | high (default: rough)communication_buffer_percent: extra coordination/communication time percentage (default: 10)devops_extra_requirements: deployment extras such as autoscaling, blue-green, canary, multi-env hardening (optional)output_dir (default: current workspace)output_date (default: current date)Before starting estimation, ask the user to provide or confirm these items:
estimation_granularity (page | feature | function)team_profile (advanced-developer | senior-developer | mixed-team)
advanced-developer: experienced engineer comfortable with full-stack and DevOps; fastest pacesenior-developer: solid engineer, may need minor ramp-up on unfamiliar areas; moderate pacemixed-team: team with varied experience; slowest pace, more coordination overheadconfidence_target (rough by default)communication_buffer_percent (10% default, user can override)devops_extra_requirements for deployment (if none, state none)unknown)If any item is missing, pause and request it explicitly before estimating.
When source_file_path is provided:
.pptx: extract text from each slide in order. Treat each slide as a potential scope section. Preserve slide titles as section headers..docx: extract full text content preserving heading structure.python-pptx, python-docx, pandoc, or equivalent) to extract text. If no extraction tool is available, stop and inform the user.scripts/validate-inputs.sh
../_shared/scripts/convert-md-to-pdf.sh
Before building any scope inventory, perform a deep-dive analysis on the parsed source content to surface the real implementable requirements. Raw inputs (especially slide decks, brief texts, or business-oriented docs) often hide, omit, or vaguely describe what actually needs to be built.
explicit — directly stated in sourceimplicit — logically necessary but not statedambiguous — stated but unclear; needs user clarificationmissing — commonly expected but absent from sourcePresent a Requirement Discovery Report to the user containing:
Wait for user confirmation or clarification on the discovery report before proceeding to scope inventory. If the user dismisses a discovered requirement, remove it from scope. If the user confirms an implicit or missing requirement, promote it to confirmed scope.
scripts/validate-inputs.sh and run the mandatory pre-run intake to collect missing preparation inputs.Scope Confirmation to the user and request confirmation/update.page: page/screen-level tasksfeature: module/feature-level tasksfunction: endpoint/function-level tasks
12a. Scope coverage verification — before finalising the breakdown, cross-check every item in ## Scope Confirmation against the draft task list:page granularity, logically group pages that share a template or content type (e.g., same section of the site), but list the covered page names explicitly in the task description so coverage is visible.rough: 30%normal: 20%high: 10%communication_buffer_percent (default 10%).skills/_shared/scripts/convert-md-to-pdf.sh.All output — including the Requirement Discovery Report, Requirement Summary, Scope Confirmation, Assumptions, Implementation Breakdown, Disclaimer, and every other section — must be written in the same language as the original source input. Detect the language of the source text (or extracted document content) and use that language consistently throughout the entire output. Do not translate or switch to English unless the source input is in English.
project-estimate-<project-name>-<YYYY-MM-DD>.md
Generate <project-name> slug using the shared slug rule in skills/_shared/references/slug-rule.md.
Use this section order exactly:
# Project Estimate: <project_name>## Requirement Discovery Report## Requirement Summary## Scope Confirmation## Assumptions## Estimation Granularity## Implementation Breakdown## Risk Buffer and Communication Buffer## Total Estimate (Optimistic / Expected / Conservative Workdays)## Disclaimer## Dependencies Required## Requirement Discovery Report requirements:
explicit, implicit, ambiguous, missing.## Requirement Summary requirements:
## Scope Confirmation requirements:
confirmed or pending.pending.## Estimation Granularity requirements:
Disclaimer and Dependencies Required.simple: straightforward CRUD/configurationmedium: moderate business logic or integration complexitycomplex: multi-system, high uncertainty, or critical workflowsThe user's selected definition-of-done scope controls which task categories appear:
code: include page/feature/function implementation tasks and API integrationtests: include a Testing row in the implementation breakdown (unit, integration, e2e as appropriate)documentation: include a Documentation row (README, API docs, inline docs)deployment baseline: include deployment/devops tasksOmit categories the user excluded. If the user chose only code, do not add testing or deployment rows.
estimation_granularity.## Scope Confirmation is traceable to at least one implementation breakdown task; no confirmed page or feature is silently omitted.page granularity with grouped tasks, covered page names are visible in the task description or a dedicated note (e.g., parenthetical list of page slugs or names).Implementation Breakdown.Input:
project_name: member-portalsource_file_path: /path/to/member-portal-requirements.pptxestimation_granularity: pageconfidence_target: normalOutput:
project-estimate-member-portal-YYYY-MM-DD.md