Loading...
Loading...
Found 6 Skills
Evaluate strategic options by NPV vs ease of implementation. Use for project prioritization, resource allocation, and strategic decision making.
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.
Decision-making framework for software development, Y Combinator / Silicon Valley style. Based on real principles from Paul Graham, Sam Altman, Michael Seibel, Patrick Collison, and Brian Chesky. Use when: - Developing features or products - Making technical decisions (what to do, how, when) - Prioritizing work (P0, P1, P2) - Evaluating whether to refactor or patch - Deciding on technical debt - Evaluating whether to add tests, CI/CD, or automation - Any architecture or engineering decision Triggers: development, code, feature, refactor, architecture, prioritize, technical decision, what to do first, technical debt, tests, CI/CD, sprint, backlog
Before committing scarce time, people, or money, name the best forgone use of those resources and the value delta of the chosen path versus that alternative.
Prompt the user with pointed questions to extract what is in their head about a project — remaining work, what is being avoided, what really matters, what does not. Use when the user says "prompt me", "ask me questions", or wants the agent to figure out priorities by questioning them.
Decide what the go-to-market team works on this week: every Monday last week's work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull request per initiative, or one workspace pull request when there are none. Triggers: "what should we work on this week", "are the bets we already have on track", "what should we do next this week", "rank our initiatives against what is actually running", "weekly GTM plan from the cadence log", "recommend next work from infra and runs", "the play is deployed but I don't think it ran". Cargo project, defineAgent, harness claudeCode, GitHub, cargo-ai CLI reads, initiatives, cadence. Skip when: you want today recapped and posted to Slack, which is standup; or you want call transcripts scribed into context, which is call-capture.