development-estimation

Use when estimating time, effort, or complexity for features or projects - provides structured estimation workflows with breakdowns, risks, and confidence intervals.

Jump to install Review files

Repository: NickCrew/Claude-Cortex
Last source activity: April 23, 2026 at 21:56
Detected SKILL.md language: English
Stars: 62
Forks: 15

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/NickCrew/Claude-Cortex/tree/main/skills/development-estimation.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/NickCrew/Claude-Cortex --skill development-estimation

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

name: development-estimation
description: Use when estimating time, effort, or complexity for features or projects - provides structured estimation workflows with breakdowns, risks, and confidence intervals.
keywords: ["complexity estimate","effort estimate","estimate effort","scoping","t-shirt size","time estimate"]
file_patterns: ["**/TODO.md","**/docs/plans/**","**/notes/**","**/planning/**","**/scenarios/**","**/todo.md"]
confidence: 0.7

# Development Estimation ## Overview Create consistent, defensible estimates by breaking scope into components, identifying risks, and providing confidence intervals. ## When to Use - Estimating feature or project scope - Providing effort or complexity estimates - Delivering risk-aware breakdowns Avoid when: - The task is trivial or a rough gut-check is sufficient - Requirements are unknown and need discovery first ## Quick Reference | Task | Load reference | | --- | --- | | Estimation workflow | `skills/development-estimation/references/estimate.md` | ## Workflow 1. Define scope and estimation type (time/effort/complexity). 2. Load the estimation reference for structure. 3. Break into components and dependencies. 4. Add risks and confidence intervals. 5. Deliver estimate with assumptions. ## Output - Estimate with breakdown and confidence interval - Assumptions, risks, and validation notes ## Common Mistakes - Estimating without clear scope - Ignoring risk and dependency factors - Overstating precision beyond available data

View on GitHub

Back to search Back to installation

agent-loops

Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.

2026-06-29

design-journey-review

Combined visual design and user journey review: color systems, typography, spacing, information density, visual hierarchy, workflow stages, emotional curve, friction points, and daily-use optimization. Use when evaluating how an interface looks, how it serves its user over time, and whether the design earns its space.

2026-06-29

knowledge-stack

Use this skill whenever working inside any of Nick's repos (under ~/Developer/) or whenever a conversation touches Nick's durable cross-cutting work — Atlas Crew product strategy/brand/planning, the Unanet job, job search, interviews, tax amendment, foreclosure/tenant situation, strategic positioning. Maps Nick's three Basic Memory projects (products, work, main) and the per-repo dev trackers, and says which layer owns which kind of question. Consult before reasoning from stored memory summaries about repo architecture, product decisions, active priorities, or ongoing personal/career state — stored memory is lossy; the trackers and the Basic Memory projects are the real artifacts and should be consulted first.

2026-06-29

View all from this repository

development-estimation

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository