Loading...
Loading...
Found 8 Skills
Use quando uma spec em draft, defined, planned, in-progress ou review precisar de conversa para resolver lacunas, recalibrar Effort ou registrar respostas confirmadas antes da próxima transição. Não use para capturar Inbox sem perguntas, executar implementação, aprovar gates ou mover pastas diretamente.
Transform specifications into implementation plans with architecture design and dependency-ordered tasks. Use for spec-to-plan conversion, task breakdown, effort estimation. Skip if no spec exists.
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.
UiPath automation discovery — mines Slack/email/wikis/CRM/HRIS/ERP for repetitive work, SPOFs, and replicable models; produces a 4-tier prioritized opportunity report with UiPath implementation paths, then sizes build effort (complexity band → pack-hours → contingency). Use to discover automation opportunities, find what to automate, estimate/size a delivery, or run an internal automation audit across an organization. For building a specific automation→uipath-rpa, authoring a Flow→uipath-maestro-flow, working with agents→uipath-agents.
Estimation techniques including analogous, parametric, three-point, and expert judgment methods. Provides effort, cost, duration, and complexity estimates for projects, features, and tasks.
Estimate khối lượng công việc của một dự án phần mềm bằng man-day. Dùng khi user cung cấp functional requirements (danh sách công việc) + techstacks và muốn ước lượng effort. Quy trình 3 bước (Sizing FE/BE → Manday Build → Full SDLC) cho Mid-level dev, output bảng markdown.
Use when a long task or issue description needs a concise team-facing version for estimation while preserving full requirements in a standalone developer guide.
Review data, issues, code, and git history; present options with effort and one-way/two-way door labels; recommend one path and name the right fix (explain if they differ). Use before implementing when a decision needs evidence-backed options.