Packs

3 packs

@brycewang-stanford

Twelve RSS-specific skills for the single-track robotics flagship: science-first framing, OpenReview mechanics, the two-stage review with invited rebuttals, and free open-access proceedings, grounded in the RSS 2026 Sydney cycle.

2 skills · pack

@brycewang-stanford

Twelve-skill bundle covering the Science manuscript lifecycle: workflow router, scope/significance fit, advance framing, abstract + one-sentence summary, main-text writing, display items, statistics & reproducibility, data/materials/code availability, reference style, cover letter, submission preflight, and reviewer rebuttal.

2 skills · pack

@brycewang-stanford

Twelve-skill bundle covering the Cell manuscript lifecycle: workflow router, scope/significance fit, single-narrative framing, the Highlights + eTOC + Graphical Abstract trio, the ≤150-word Summary, main-text writing, display items, STAR Methods + Key Resources Table, data/code availability, Cell Press author–date references, submission preflight + cover letter, and reviewer rebuttal.

9 skills · pack

Results for “framing”

11 skills

problem-framing-canvas

Guide teams through MITRE's Problem Framing Canvas to clarify problem statements before jumping to solutions.

Trigger: PRD, product requirements, spec, problem framing, project scoping, roadmap. Scope: Creating and updating product requirement documents and framing problem scopes. Boundary: Excludes code implementation, design mocks, or CI/CD config.

discovery-process

Guide product managers through a complete discovery cycle from problem hypothesis to validated solution using problem framing, customer interviews, synthesis, and experimentation.

opportunity-solution-tree

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

More results

prd-development

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

epic-hypothesis

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

altitude-horizon-framework

Diagnose the PM-to-Director transition using altitude (scope) and horizon (time) axes, identify transition zones, and apply the Cascading Context Map when organizational direction is vague.

design-sprint-plan

Plan and facilitate design sprints from challenge framing through prototype testing, using a structured 5-day process with variations for mini, remote, and discovery sprints.

product-strategy-session

Guide product managers through a comprehensive strategy session covering positioning, discovery, and roadmap planning to move from vague direction to validated strategy.

problem-statement

Write a user-centered problem statement that captures who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.

theheavenlyd3mon

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.