Loading...
Loading...
Found 16 Skills
Estimate project scope, timeline, and resource requirements using multiple estimation techniques including bottom-up, top-down, and analogous estimation methods for accurate project planning.
دستیار برآورد پروژه‌های نرم‌افزاری برای کارفرمای ایرانی: مقایسه‌ی راه‌حل‌ها با تحقیق (ساخت سفارشی، سرویس آماده، low-code)، برآورد ساعت و هزینه با روش سه‌نقطه‌ای، نقش‌ها و اندازه‌ی تیم، هزینه‌ی میزبانی و سرویس‌ها و نگهداری بعد از تحویل، زمان‌بندی شمسی، قیمت درخواست تغییر و پلن پشتیبانی. هر وقت کاربر پرسید یک پروژه چقدر طول می‌کشد، چه نیرو یا تیمی لازم دارد، کدام راه‌حل یا تکنولوژی مناسب‌تر است، هزینه‌ی سرور و سرویس‌ها چقدر است، یا قیمت یک تغییر را خواست، از این Skill استفاده کن، حتی اگر کلمه‌ی برآورد را نگفت (مثلاً «این چقدر کار داره؟»، «تنهایی می‌رسم؟»، «وردپرس بزنیم یا از صفر؟»). مرحله‌ی ۳ دستیار پروپوزال (software-proposal-assistant) برآورد را به این Skill می‌سپارد. Use for effort and cost estimates, build vs buy, staffing plans, hosting and running costs, schedules and change request pricing.
When provisioning, setting a limit, or committing an estimate under uncertainty, size a buffer to residual error and the cost of breach—not to the optimistic edge.
Direct technical advisor mode for counting/estimation and architecture/design
Produces calibrated three-point PERT estimates (best/likely/worst) with confidence intervals, unknowns, and assumptions. Triggers on: "estimate this", "how long will this take", "effort estimate", "confidence interval", "story points", "t-shirt sizing". NOT for task decomposition, use task-decomposer.
Break down large tasks into smaller, actionable items. Use when planning sprints, estimating work, or creating implementation plans. Covers task breakdown strategies.
Skill para estimar proyectos de software y generar documentos Word profesionales. Genera estimaciones con tiempo en meses, equipo propuesto (rol y porcentaje de dedicación), consideraciones técnicas, y warnings/riesgos. Incluye template .docx corporativo. Usar cuando el usuario pida estimar un proyecto, calcular tiempos, definir equipo necesario, generar documento de estimación, o frases como "cuánto tiempo llevaría", "qué equipo necesito", "estimar proyecto", "presupuesto de tiempo", "planificar desarrollo", "documento de estimación".
Translate discovered client pain points into high-level technology solution architectures for consulting engagements in Software Engineering, Data Platforms, and AI/ML. Produce solution briefs with phased roadmaps, effort estimations, team composition, and technology recommendations. Use when designing a pre-sale technical solution, creating a solution brief for a proposal, or when a prospect needs to understand what the engagement would look like before committing. This is the preventa técnica / solution engineering step.
Use when estimating time, effort, or complexity for features or projects - provides structured estimation workflows with breakdowns, risks, and confidence intervals.
Estimation techniques including analogous, parametric, three-point, and expert judgment methods. Provides effort, cost, duration, and complexity estimates for projects, features, and tasks.
Helps engineering managers plan roadmaps, prioritize work, and communicate priorities effectively — produces the 20% tech debt framework (and its 5 traps), a phased release pressure-test, a maintenance cost model, the Always Green delivery method, sprint anti-patterns, hidden costs of custom features, a critical deadline playbook, the Iron Law of Projects with reference-class forecasting, a "no technical projects" framing, and feature factory warning signs. Use when the user says "roadmap," "quarterly planning," "OKRs," "prioritization," "what should we work on," "planning cycle," "backlog grooming," "stakeholder alignment," "capacity planning," "technical debt," "we're always late," or "leadership doesn't understand engineering work."
Help users set and hit realistic deadlines. Use when someone is planning project timelines, struggling to hit deadlines, dealing with timeline pressure from stakeholders, or trying to improve estimation accuracy.