Explore skills
Showing 12871–12900 of 77079 skills
Draft and score quarterly OKRs: a qualitative objective, measurable key results and a counter-metric. Use when setting or reviewing a team's OKRs before they are committed, or when KRs read like a task list.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexWrite an 8-section product requirements document, framing the problem before the solution. Use when specifying a new product or a large feature that needs engineering, design and business aligned on one document.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexCluster, score and route inbound feature requests from support, sales, NPS and exec asks, and draft honest replies. Use when a feedback queue needs triaging or a customer needs a defensible yes, no or exploring answer.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexCompute lead time, cycle time, throughput, WIP, aging WIP and a cumulative flow diagram from issue status history. Use when diagnosing slow delivery, setting WIP limits or preparing a flow review.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexTurn a blocked decision into an async questionnaire a stakeholder can answer without a meeting. Use when you need someone else's input to decide, a meeting would be overkill, or answers from several people must be consolidated.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexTrack cross-team dependencies in one JSON file and get a risk-ranked blocker list, the longest hand-off chain and a Mermaid graph. Use when several teams depend on each other and you need to know what to chase this week.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexMove engineering issues and external PRs through a triage state machine and write agent-ready briefs. Use when clearing a triage queue, deciding if a report is real or wanted, or handing an issue to a coding agent.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexWrite When/Want/So backlog stories from observed user situations, gated on INVEST and outcome-focused acceptance criteria. Use when writing backlog items from research or converting "As a..." user stories to job stories.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexPick the one metric that tracks customer value, decompose it into inputs with leading indicators and guardrail metrics. Use when defining the metric a team optimises before writing OKRs, or when a dashboard has no headline.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexTurn a feature-list roadmap into outcome statements placed in Now/Next/Later, and check each has a measure. Use when converting a feature-list roadmap, reviewing a roadmap before it goes to leadership, or quarterly planning.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexPick a prioritization method and rank a backlog: RICE, ICE, opportunity, MoSCoW and weighted scoring, plus four reference-only methods. Use when ranking features, problems or initiatives against each other.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexTurn tickets, changelogs and git logs into user-facing notes grouped by type, breaking changes first. Use when announcing a product release, maintaining a changelog, or rewriting technical entries for customers.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexBuild and audit the plan for one iteration: goal, real capacity, commit vs stretch, dependencies, risks and definition of done. Use when planning the next sprint or auditing a plan for a team that keeps missing its sprints.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexMaps stakeholders by power, interest and stance, then plans engagement and blocker conversion so objections surface early. Use for a major initiative, an enterprise deal, a re-org or a contested roadmap change.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexRenders a weekly executive status update (highlights, blockers, risks, asks, next) from Jira or Linear data. Use when preparing a sponsor or steering update, or standardising a team's weekly report.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexTurns meeting notes or transcripts into a summary of decisions, owned and dated action items, and open questions. Use when writing up a meeting, a recap email or a decision log; for patterns across a series use meeting-analyzer.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexWrites QA cases from a feature spec across happy, edge, error, empty, concurrent, accessibility and security paths, then audits coverage. Use when planning QA for a feature, or finding coverage gaps after an incident.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexChart work too big for one sprint as a map of decision tickets, resolve them in dependency order, then turn answers into tracer-bullet tickets. Use when the route is unclear, open questions block each other, or estimates swing wildly.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexWrites and grades Why-What-Acceptance backlog items so each one traces to an OKR and passes INVEST before a sprint. Use when writing backlog items, checking sprint readiness, or finding work that serves no objective.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexBuilds and audits a go-to-market plan: beachhead, motion matched to ACV, funded channels, tested messaging, owned metrics and a T-90 launch sequence. Use when launching a product, entering a segment or fixing a stalled GTM.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexDefines which accounts to sell to across eight dimensions with explicit exclusions, then scores real accounts against that profile. Use when defining or refining an ICP, building a qualification rubric, or diagnosing poor pipeline.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexConfigures Jira projects, workflows, boards, JQL, automation and dashboards, and audits board, issue and workflow exports. Use when setting up or fixing Jira, writing or debugging JQL, or designing automation rules.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexAdministers Linear teams, cycles, projects and triage, and writes GraphQL API calls. Use when setting up or fixing a Linear workspace, scripting bulk changes, or migrating from Jira to Linear.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexTurns meeting notes into an accountable register and diagnoses recurring meetings. Use when commitments get dropped or a series decides nothing; for a single meeting's recap use summarize-meeting.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexRuns multi-project programs: charters, governance, cross-project dependencies, benefits tracking and steering-committee reporting. Use when standing up a program, tracking its milestones and people, or preparing a steering update.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexScores portfolio health, risk exposure and resource capacity from a project JSON and frames board-ready status reports. Use when running a portfolio review, writing an executive RAG report, or rebalancing people across projects.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexData-driven sprint retrospectives from git history — velocity, cycle/lead time, contributor insights, and churn hotspots. Use to run a retrospective, analyze team velocity or throughput, or generate a retro report from commit history.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexClassifies growth bets into the four Ansoff quadrants and checks the investment mix against the company's stage. Use when prioritising growth bets, allocating a growth budget or testing a pitched "adjacent" move.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexBuilds and audits a nine-block Business Model Canvas, tracing each segment through value, channel and revenue and naming the riskiest assumptions. Use when designing, refreshing or stress-testing a business model.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodexSketches a one-page startup model as testable hypotheses: problem, early adopters, value proposition, unfair advantage, riskiest assumptions. Use at the idea, pre-product-market-fit or pivot stage, or for a fast model.
borghei/Claude-Skills
Stars: 1.1kClaude CodeCodex