Total 55,105 skills, Project Management has 2011 skills
Showing 12 of 2011 skills
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.
Guides deal operations administration—quote-to-cash coordination, deal desk intake and routing, CRM opportunity hygiene, order form and SOW assembly, approval workflows, signature tracking, and handoffs to legal, finance, and provisioning after customer signature. Use when processing a sales deal, preparing order paperwork, running deal desk checklist, fixing CRM stage/fields, coordinating signatures, or closing the loop post-signature—not for contract legal redlines (commercial-counsel), board or equity approvals (corporate-counsel), ASC 606 accounting (senior-revenue-accountant), support tickets after go-live (customer-ops-specialist), or M&A/financing closing (transaction-manager).
Use when facing a consulting challenge and needing structured methodology guidance: client anchored on wrong solution, messy problem needing structure, building a skeptic-proof recommendation, conflicting data sources, project at risk, or stuck on which approach to apply. Single entry point for all consulting playbook coaching.
Implement one prd.json task per iteration using tracer-bullet + compound mindset. Triggers on: ratatouille:.
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
Automated retrospectives — captures learnings at EPIC completion and on manual invocation. EPIC-scoped retros embed a Retrospective section in the EPIC artifact. Cross-epic and time-based retros produce standalone retro docs. Triggers on: 'retro', 'retrospective', 'post-mortem', 'lessons learned', 'debrief', 'what worked', 'what didn't work', 'what did we learn', 'reflect', or automatically after EPIC terminal transitions.
Fast-track an urgent fix through a streamlined pipeline. Skips Product/Feature Council, applies the fix, runs a focused review, and creates a PR with optional Deployment Council. Use for production bugs, security patches, or critical regressions that cannot wait for the full planning pipeline.
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
Feature specification and planning guidelines for software engineers. This skill should be used when writing PRDs, defining requirements, managing scope, prioritizing features, or handling change requests. Triggers on tasks involving feature planning, specification writing, stakeholder alignment, or scope management.
Context preservation, tiered summarization, resumability
Prepare organized packages of project files for sharing at different levels - from summary PDFs to fully reproducible archives. Creates copies with cleaned notebooks, documentation, and appropriate file selection. After creating sharing package, all work continues in the main project directory.
Implement an existing PRD (`Type: feat`/`fix`/`chore`), update tests/checks, and mark completed PRD checklist items. Triggers: implement prd, build feature from prd, execute prd checklist.