Total 50,396 skills, Project Management has 1845 skills
Showing 12 of 1845 skills
Explore requirements and approaches through collaborative dialogue before planning implementation
Manage projects, grants, milestones, and updates on the Karma protocol. Use when user says "create a project", "new project", "add a grant", "record funding", "add milestone", "complete milestone", "post an update", "project progress", "grant update", "update project", "edit project", "set up agent", "configure API key", or any on-chain project management action.
[BETA] Transform feature descriptions or requirements into structured implementation plans grounded in repo patterns and research. Use when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', or when a brainstorm/requirements document is ready for technical planning. Best when requirements are at least roughly defined; for exploratory or ambiguous requests, prefer ce:brainstorm first.
/em -challenge — Pre-Mortem Plan Analysis
/em -stress-test — Business Assumption Stress Testing
Analyze how to extend and leverage existing assets. Use for growth strategy and resource optimization.
Identify make-buy-partner relationships for key activities. Use for strategic alliances, outsourcing decisions, and supply chain optimization.
Map key activities and their relationships. Use for operational analysis and capability development.
Evaluate strategic options by NPV vs ease of implementation. Use for project prioritization, resource allocation, and strategic decision making.
M&A strategy for acquiring companies or being acquired. Covers strategic rationale assessment, target screening, due diligence frameworks, valuation methodologies, deal structure, negotiation strategy, integration planning, and post-acquisition execution. Use when evaluating acquisitions, preparing to be acquired, conducting due diligence, planning integration, negotiating deal terms, or when user mentions M&A, acquisition, merger, acqui-hire, due diligence, valuation, LOI, earnout, integration, or deal structure.
2. Create Feature Design Document
Proactive requirements gathering - systematically interviews the user to uncover ambiguities, preferences, and constraints BEFORE implementation begins.