跳转到主要内容
此内容尚未提供您的语言版本,正在以英文显示。

Shape Up

技能 已验证 活跃

Escape the build trap and endless backlogs. Use Basecamp's methodology to ship meaningful work in 6-week cycles with fixed time, variable scope. Use when: **Product planning** to replace endless backlogs; **Feature development** with clear time boundaries; **Team autonomy** when you want self-directed teams; **Scope management** when projects tend to balloon; **Startup development** with limited resources

目的

To guide teams in adopting Basecamp's Shape Up methodology for shipping meaningful work in structured 6-week cycles with fixed time and variable scope.

功能

  • Introduces shaping for defining work at the right abstraction level
  • Sets appetites over estimates for time-boxed work
  • Enables 6-week focused work cycles with 2-week cooldowns
  • Empowers teams with autonomy within defined boundaries
  • Provides guidance on running betting tables for prioritization
  • Offers strategies for dynamic scope management during build

使用场景

  • Product planning to replace endless backlogs
  • Feature development with clear time boundaries
  • Team autonomy when seeking self-directed teams
  • Scope management when projects tend to balloon
  • Startup development with limited resources
  • Agency/consulting projects with fixed timelines

非目标

  • Replacing audio engineering expertise
  • Making subjective creative decisions
  • Accessing or editing audio files directly
  • Guaranteeing commercial success

工作流

  1. Shape a feature idea by defining the problem, appetite, solution, rabbit holes, no-gos, and risks.
  2. Plan a cycle by running a betting table to select shaped projects based on strategic fit, significance, appetite, and team availability.
  3. Manage scope during build by identifying must-haves vs. nice-to-haves and cutting scope to fit the fixed time.
  4. Follow the 6-week build cycle with a 2-week cooldown period for bug fixes, technical debt, and shaping future cycles.

安装

npx skills add guia-matthieu/clawfu-skills

通过 npx 运行 Vercel skills CLI(skills.sh)— 需要本地安装 Node.js,以及至少一个兼容 skills 的智能体(Claude Code、Cursor、Codex 等)。前提是仓库遵循 agentskills.io 格式。

质量评分

已验证
100 /100
1 day ago 分析

信任信号

最近提交about 1 month ago
GitHub 所有者 guia-matthieu (opens in new tab)
星标104
许可证MIT
网站clawfu.com(opens in new tab)
状态
查看源代码

类似扩展

User Story Mapping

100

Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

技能
deanpeters

Scrum Master Expert

100

Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.

技能
alirezarezvani

Plan Sprint

99

Plan a sprint by refining backlog items, defining a sprint goal, calculating team capacity, selecting items, and decomposing them into tasks. Produces a SPRINT-PLAN.md with goal, selected items, task breakdown, and capacity allocation. Use when starting a new sprint in a Scrum or agile project, re-planning after significant scope change, transitioning from ad-hoc work to structured sprint cadence, or after backlog grooming when items are ready for inclusion.

技能
pjt222

Sprint Plan

100

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

技能
phuryn

Design Sprint

100

Test big ideas in just 5 days. Apply Google Ventures' proven methodology to go from problem to validated prototype without months of development. Use when: **New product concepts** that need validation before building; **Big feature decisions** with significant investment required; **Stuck teams** needing to break through analysis paralysis; **Startup pivots** when direction is uncertain; **High-risk bets** where failure is expensive

技能
guia-matthieu

Systematic Debugging

100

Systematic debugging methodology emphasizing root cause analysis over quick fixes

技能
bobmatnyc