メニュー
Digest the outputs archive into durable context. Use for the weekly GTM review, or whenever asked what happened recently and what we learned. Reads recent outputs entries, summarizes results, and proposes context updates as a PR. This is the repo's memory flywheel.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | weekly-review |
| description | Digest the outputs archive into durable context. Use for the weekly GTM review, or whenever asked what happened recently and what we learned. Reads recent outputs entries, summarizes results, and proposes context updates as a PR. This is the repo's memory flywheel. |
outputs/ is what happened. context/ is what we know. This skill moves
learning from the first to the second, so the repo gets smarter every week.
Collect. List outputs/ entries from the last 7 days (directory names
start with the date). Read each entry's summary.
Summarize. Write outputs/YYYY-MM-DD-weekly-review/README.md with:
Extract durable learning. For each finding that changes what we know, propose the matching context edit:
context/objection/<slug>.md.context/client/ and
context/proof/.context/signal/<slug>.md.context/motion/.
Apply the repetition rule: a claim goes into context after it shows up
independently at least twice. Once is an anecdote.Ship. One PR: the review entry in outputs/ plus the proposed context
edits. The PR description separates "observed" (outputs) from "concluded"
(context changes) so reviewers can push back on conclusions.
Turn something heard in the field into durable context, at the right confidence level. Use when the user relays an objection, a competitor mention, a win or loss reason, a signal, or any claim from a call, and asks to remember it. Enforces the repetition rule and the confidence ladder.
Audit and repair the context layer. Use when asked to clean up context, before a quarterly review, or when the knowledge graph feels stale. Finds missing frontmatter, broken references, orphan files, and stale content, then fixes them file by file.
How this GTM repository works. Load when orienting in this repo, deciding where a change belongs, or explaining the layer conventions to someone. Covers the layers, the dependency direction, the PR workflow, the confidence ladder, and where each kind of change goes.
Write today's entry in the cadence log. Use at the end of a working day, or when the user recaps what happened. Captures what moved, what is stuck, and anything worth remembering, then routes stuck items to carryover and repeated observations toward context.
Scaffold a new GTM motion end to end across all three layers. Use whenever creating a new motion, campaign, play, or automation in this repo, so the narrative (context), the implementation (infra), and the regression suite (evals) ship together and never drift apart. Enforces the outreach hypothesis rule.
Plan the coming week in the cadence layer. Use every Monday, or whenever asked what this week should focus on. Pulls from plan/ and open initiatives/, carries over unresolved items, and writes cadence/weekly/YYYY-Www.md. Escalates anything that has slipped three weeks into a decision instead of a task.