Stats
Actions
Tags
From cross-functional-leadership
Work with product to negotiate achievable scope when capacity is constrained.
How this command is triggered — by the user, by Claude, or both
Slash command
/cross-functional-leadership:negotiate-scope requested features team capacity timelineThe summary Claude sees in its command listing — used to decide when to auto-load this command
Chain these steps: 1. Use the `scope-negotiation` skill to explore viable options with product 2. Use the `technical-requirements-translation` skill to explain capacity constraints in business terms 3. Use the `technical-product-partnership` skill to build shared ownership of the decision 4. Synthesize into agreed scope with clear rationale and next steps After completion, suggest: - How to prioritize within agreed scope - How to identify "scope for later" and get it on roadmap - How to measure success against negotiated scope
Chain these steps:
scope-negotiation skill to explore viable options with producttechnical-requirements-translation skill to explain capacity constraints in business termstechnical-product-partnership skill to build shared ownership of the decisionAfter completion, suggest:
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-cross-functional/product-managerAdopts product manager persona to clarify requirements, manage priorities, align stakeholders, scope features, prioritize tasks, and generate user stories from the request.
/prp-prdGenerates a product requirements document through iterative problem discovery, market research, and hypothesis-driven questions.
/feature-prioritization-frameworkPrioritizes product features using RICE, MoSCoW, and Kano frameworks against objectives, value, effort, and constraints. Produces a detailed roadmap with build, defer, or kill rationale.
/scopeInteractively scopes features or improvements via collaborative dialogue, generating a scope document clarifying IN/OUT boundaries, user value, and decisions in concepts/scope.md.