weekly-planning
Decide what the go-to-market team works on this week: every Monday last week's work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull request per initiative, or one workspace pull request when there are none. Triggers: "what should we work on this w
as observed 2026-11-17T01:34:38.316Z- Identifier
weekly-planning- Source
- ClawHub
- Version observed
- 0.2.0
- Source repository
- not published
- Repository observation
- No source repository listed
- First observed here
- 2026-09-29T04:47:03.526Z
- Observations recorded
- 5
- Installs (reported upstream)
- 0
- Weekly downloads (upstream)
- 570
- Declared license
- MIT-0
Observation history
2026-11-17T01:34:38.316Z
Fields that differed: changelog latestVersion summary
| Field | Before | After |
|---|---|---|
changelog |
"- Updated CLI and project terminology from \"CDK\"/\"workspace\" to \"project\" throughout documentation and instructions.\n- Adjusted compatibility and install instructions to re | "- Updated compatibility requirements to CLI 1.0.154+ and CDK 1.0.150+, including connected-state harness binding and top-level `env` configuration.\n- Added “are the bets we alrea |
latestVersion |
"0.1.3" | "0.2.0" |
summary |
"Decide what the go-to-market team works on this week: every Monday last week's work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull req | "Decide what the go-to-market team works on this week: every Monday last week's work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull req |
2026-10-19T22:50:38.750Z
Fields that differed: changelog latestVersion summary
| Field | Before | After |
|---|---|---|
changelog |
"Version 0.1.2 of weekly-planning focuses on clarifying triggers and simplifying documentation.\n\n- Expanded trigger list in skill description to better reflect usage scenarios\n- | "- Updated CLI and project terminology from \"CDK\"/\"workspace\" to \"project\" throughout documentation and instructions.\n- Adjusted compatibility and install instructions to re |
latestVersion |
"0.1.2" | "0.1.3" |
summary |
"Decide what the go-to-market team works on this week: every Monday last week's work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull req | "Decide what the go-to-market team works on this week: every Monday last week's work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull req |
2026-10-18T21:45:32.509Z
Fields that differed: changelog latestVersion summary
| Field | Before | After |
|---|---|---|
changelog |
"## weekly-planning 0.1.1\n\n- Added example output to documentation for clarity on generated recommendations and pull requests.\n- Declared intended audience with personas: sales- | "Version 0.1.2 of weekly-planning focuses on clarifying triggers and simplifying documentation.\n\n- Expanded trigger list in skill description to better reflect usage scenarios\n- |
latestVersion |
"0.1.1" | "0.1.2" |
summary |
"Every Monday last week's GTM work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull request per initiative — or one workspace pull reques | "Decide what the go-to-market team works on this week: every Monday last week's work is ranked against active initiatives, declared infra, and live runs, as one reviewable pull req |
2026-09-30T05:46:36.081Z
Fields that differed: changelog latestVersion
| Field | Before | After |
|---|---|---|
changelog |
"Weekly-planning skill v0.1.0 initial release:\n\n- Automates weekly planning by generating reviewable pull requests every Monday, ranking last week’s GTM work against initiatives, | "## weekly-planning 0.1.1\n\n- Added example output to documentation for clarity on generated recommendations and pull requests.\n- Declared intended audience with personas: sales- |
latestVersion |
"0.1.0" | "0.1.1" |
Correction
If you maintain this extension and believe anything above is inaccurate, request a correction. Corrections are published, and disputed entries are marked as disputed while under review.