Claude Skills by OutlineDriven

Use when the user says "shape this", "pitch this", "gut check the shape", "fix this pitch", or asks whether a result matches the bet. Shapes work into a fat-marker pitch with five ingredients: problem, appetite, solution, rabbit holes, no-gos. Not for tasks requiring source or remote-system changes; not for detailed implementation plans — use plan.

Use when a settled plan needs implementation tickets published as blocker-linked slices, tracer bullets, or expand-contract sequencing, and a human invokes the publication. Publishes GitHub issues or local ticket files and writes their URLs back into the plan. Not for implementation — use work; not for unsupervised publication.

Use when a message contains `TODO ADD: <requirement>`, adding it to the durable source and the native todo in the same turn. Not for deepening coarse task lists — use todos-enhance; not for re-syncing stale lists — use todos-update; not for retitling, reordering, or completing existing todos.

Use when the user says the tasks are too vague or asks to sophisticate the todos, or the list reads as headings rather than executable work. Not for stale-list reconciliation — use todos-update; not for adding requirements — use todo-add.

Use when the user asks to update the todos, resync the task list, or say what to do next, or the plan and the tree have drifted apart. Not for deepening coarse lists — use todos-enhance; not for adding requirements — use todo-add.

Use when a greenfield project or large feature build will not fit in a single agent session. Charts a route by naming the destination, mapping the fog, and graduating decision tickets on the frontier. Don''t use for implementation, remote credential changes, or work that fits in one session.

Use when projecting cost, estimating BYO cost or spend, or sizing a deal. Delivers a projection with pricing model, run-rate, scenario comparison, conversion assumption, and sensitivity grid. Not for remote, credential, publish, deploy, or irreversible changes.

Use when defining product strategy, starting or redirecting a product, or repairing stale STRATEGY.md. Interviews the user with reject-by-default pushback against a drafted strategy document, then writes accepted updates back. Not for project plans, roadmaps, scheduling, or work needing no interview.

Use when a user asks for a product spec with numbered behavioral invariants. Writes PRODUCT.md with unambiguous, implementable behavior. Not for evidence-backed PRDs and PR creation — use write-prd; not for implementation plans — use write-tech-spec.

Use when a user asks to execute or investigate a PromQL expression against a Prometheus server. Returns query results in the requested format or a classified failure diagnosis. Read-only HTTP queries only; no source or remote-system changes.

Use when reviewing Django performance, N+1 queries, or queryset behavior. Returns validated ORM findings with severity-matched impact and concrete rewrites. Not for authorization or IDOR review — use django-access-review. No source or remote-system changes.

Use when creating or migrating a Python project or script to uv, Ruff, ty, and pytest. Handles single-file scripts, multi-file projects, reusable packages, and migrations from legacy tooling. Not for pushing to a remote or publishing — use new-branch-and-pr for that.

Use when removing modules from pyproject mypy exclusions or running a typing-debt worker batch. Fixes surfaced typing issues in scope and returns a batch summary backed by passing targeted mypy, tests, and pre-commit. Not for cross-team or out-of-scope typing work.

Use when the user asks for a council, second opinions, or parallel investigation. Spawns parallel subagents from distinct stances, returns a decision memo. Not for cross-examination of existing proposals — use cross-critique.

Use when independent proposals on a contested decision need structured cross-critique before choosing. Reuses original authors and synthesizes convergence, objections, and the surviving option. Not for parallel multi-stance investigation — use council.

Use when one reviewer is not enough because failure modes are heterogeneous, or a claim needs cross-lens pressure before it ships. Returns a convergence picture with per-lens verdicts and the single resolving question. Not for collapsing a decision field — use converge.

Use when the user asks to research a topic and produce a thorough sourced report. Produces a prose-first cited Markdown report with key findings, recommendations, and risks. Don''t use for remote, credential, publish, deploy, or irreversible changes.

Use when a user suspects the current direction is tunnel-visioned or inherited its framing: spawn 2-5 independent reads, classify each, cluster by shared root, and surface divergent-incompatible reads first. Not for framing-bias checks on a question — use prism.

Use when asked to "interrogate" or run an adversarial multi-model review of a supplied code artifact. Returns an act/consider/note/dismiss verdict with an agreement map. Don''t use for tasks that require source or remote-system changes.

Use when the user asks why a plan is wrong or says "poke holes in this". Returns one load-bearing objection and the cheapest experiment that would prove whether it matters. Don''t use for tasks that require source or remote-system changes.

Use when one reviewer angle is insufficient or the user asks to prism an artifact or review it from different angles. Selects independent lenses, strips session framing, fans out fresh zero-context reads, and reports divergences before convergences with one decisive resolving question. Not for source or remote-system changes.

Use when invoking /product-signal-pulse with an optional lookback window to query configured product signals. Resolves config, runs a first-run interview if unconfigured, dispatches read-only queries to analytics, tracing, and payment sources, and writes a 30-40 line pulse report under docs/pulse-reports. Not for credential, publish, deploy, or irreversible changes.

Use when asked to investigate design rationale, regression causes, or thresholds via source playbooks. Produces a confidence-tiered cited narrative with unknowns retained. Not for why-style decision rationale from conversation context — use why.

Use when asked to analyze a screen recording, voice capture, or meeting notes artifact for product feedback. Routes to a quick bug report or extensive analysis with timestamped evidence artifacts and a brainstorm handoff. Not for credential, publish, deploy, or irreversible changes.

Use when invoked as visual-fact-check with a document path. Verifies every factual claim against its cited sources, corrects errors in place, and appends a verification summary. Not for both-ways fact-checking of assertions — use verify-both-ways.

Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body with human approval and preview. Not for automated or model-initiated insertion without explicit human review.

Use when a verified non-trivial fix lands. Automatically captures a durable learning doc to docs/solutions/ or a CONCEPTS.md entry, or determines nothing qualifies. Also handles refresh when solution docs may have drifted. Not for unverified fixes.

Use when the user wants the current jargon weather of a domain described without advocacy. Surveys circulating terms, their signaling freight, and their usage trajectory from verifiable external sources. Not for choosing a positioning move — use buzzword-hijack.

Use when the user asks "where to help", "contribution opportunities", or "find a good first issue". Returns two to five data-backed recommendations each naming a file, a reason, and an executable first step.

Use when the learner is ready to apply cleared concepts in a real project. Scopes one capstone sized to those concepts, writes capstone-<slug>.md, yields to the learner to build it, then judges the returned work item by item on a later visit. Not for exercises or quizzes — use drill.

Use when the human returns after a gap, cannot follow the project, or asks what happened. Returns a screen-length briefing grounded in live state. Also handles pre-decision orientation when the mental model is stale. Not for initial onboarding — use onboard.

Use when the user asks to summarize competitor changelogs or analyze recent competitor releases into a deduplicated report opened as a PR. Not for researching a specific feature across competitors — use competitor-feature-research.

Use when the user asks to research a specific feature across competitor products and publish a cited report. Not for summarizing changelogs — use competitor-changelog.

Use when the user explicitly asks to save, curate, or consolidate what was learned, or closes a meaningful knowledge-work session. Curates at most three typed, approved knowledge records from existing lessons into docs/knowledge/, checks for duplicates and contradictions, and confirms by naming retrieval tags. No remote, publish, deploy, or irreversible mutation.

Use when the user asks to rank deployment platforms and stacks against their product with quantitative trade-offs. Enumerates candidates, gathers raw metrics, normalizes them to a common scale, applies user weighting, and returns a ranked list with per-axis scores. Read-only; no source or remote mutation.

Use when a long session has accumulated stale or conflicting context or when the user asks to refresh it. Rechecks context against source and drops stale items so the acting context is provably current and minimal. No remote, credential, publish, deploy, or irreversible mutation.

Use when asked to mine prior chats on a scheduled or watcher tick and maintain project memory. Reads transcripts and the memory index, extracts decisions and conventions, filters against the baseline, and writes deduplicated high-signal updates or reports no update. No remote, credential, publish, deploy, or irreversible mutation.

Use when asked to create a multi-session learning plan. Returns a milestoned plan, practice, and review rubric. Don''t use for tasks that require source or remote-system changes.

Use when Survey and Job Culture Index profiles need analysis for stress, burnout, disengagement, or flight-risk signals. Calculates energy utilization, trait shifts, and a defined risk level from the paired charts, with nonclinical recommendations. Not for clinical diagnosis — use a qualified clinician.

Use when two colleagues'' working friction needs trait-based explanation, accommodations, process changes, and escalation boundaries. Also handles manager-report friction when both profiles exist. Not for performance adjudication — use the organization''s formal process.

Use when a predicted Culture Index profile needs comparison with role requirements, team composition, and manager profile to inform a hiring decision. Maps trait matches and confidence to numeric scores, produces a recommendation on a defined ladder, and names verification areas. Not for transcript prediction — use culture-interview-profile-prediction.

Use when asked to predict Culture Index traits from an interview transcript before a survey exists. Also handles uncertain traits when evidence is sparse or contradictory. Not for interpreting completed survey results.

Use when a manager needs profile-specific communication, one-on-one, motivation, and energy guidance for a direct report. Returns trait-gap adjustments, tailored cadence, and energy-risk actions. Not for general pair or team compatibility analysis.

Use when a signed new hire''s Culture Index profile and team profiles need a first-90-days plan. Returns buddy choice, friction map, manager briefing, communication preferences, 30/60/90 actions, and success indicators. Not for manager coaching — use culture-manager-coaching.

Use when customer feedback, NPS, churn, email feedback, call transcripts, or voice-of-the-customer analysis needs a report over a time window. Produces themes, pain points, competitive mentions, feature demand, exact counts, week-over-week comparison, cited links, and verbatim quotes in a report and PR. Requires human authorization for credentials, publication, and PR creation.

Use when a user wants to record why one world won over the others. The decision and its rationale are recorded in the decision diary. Don''t use for remote, credential, publish, deploy, or irreversible changes.

Use when a current decision needs pressure-testing until the rationale is clear to a skeptic. The result states the decision in plain terms or names the exact gap that prevents a defensible explanation. Don''t use for tasks that require source or remote-system changes.

Use when dogfooding a developer-facing product or workflow to produce an evidence-backed eight-dimension DX scorecard with measured time to hello world and prioritized fixes. Not for visual UI audit — use web-design-review.

Use when reviewing a prose plan, spec, PRD, requirements doc, design doc, or brainstorm, or invoking /doc-review. Returns tiered findings with verbatim evidence without editing the document. Not for collaborative drafting — use doc-coauthoring. No remote or irreversible changes.

Use when making an architectural decision, changing a public API, or shipping a feature needing rationale. Produces ADRs, inline gotchas, README/API docs, and changelog entries. Not for structured doc authoring — use docs-writing; not for PR-based doc sync — use docs-update.