본문으로 건너뛰기
cccskills
무료GitHub에 공개

weekly-review

Synthesize a week of inputs (calendar, tasks, journal, OKR check-ins) into a structured review with wins, learnings, blockers, and next-week priorities. Use for a Friday/Sunday weekly review, GTD review, or OKR check-in.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(4)

  • SKILL.md3.5 KB
  • assets/weekly_review_input.json2.5 KB
  • references/weekly_review_methodology.md5.3 KB
  • scripts/weekly_review_synthesizer.py4.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Weekly Review

Synthesize a week into a structured review covering wins, learnings, blockers, and next-week priorities.


Keywords

weekly review, GTD, getting things done, OKR check-in, retrospective, weekly retro, journal, reflection, end of week, EOW


Clarify First

Before synthesizing the review, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • The week's raw inputs — actual wins, learnings, and blockers; this is the content the review synthesizes, not invented
  • OKR / goal progress — current numbers vs target drives the check-in section and flags drift
  • Next-week priorities — the top 1-3 commitments the review must end on

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


Quick Start

  1. Fill in assets/weekly_review_input.json with the past week's wins, learnings, blockers, OKR progress
  2. Run: python scripts/weekly_review_synthesizer.py weekly_review_input.json
  3. Save the output as your week's review

Core Workflows

Workflow 1: Standard Friday Review (30 min)

  1. Capture 3-5 wins from the past week
  2. Capture 1-3 learnings (what surprised you, what you got wrong)
  3. Capture top 1-3 blockers / risks for next week
  4. Update OKR / goal progress
  5. List top 3 priorities for next week
  6. Run synthesizer

Time Estimate: 30-45 minutes weekly.

Workflow 2: Bootstrap (First Time)

  1. Read references/weekly_review_methodology.md
  2. Decide cadence (Friday afternoon vs Sunday evening — both work)
  3. Block 30-45 min recurring on calendar
  4. Use input template; tune over 4 weeks until format works for you

Time Estimate: 1 hour to set up; 30-45 min weekly thereafter.

Workflow 3: Quarterly Pattern Review

  1. Save weekly reviews in a single folder
  2. Quarterly: read all 12-13 weeks
  3. Look for patterns: recurring blockers, energy patterns, OKR drift
  4. Adjust cadence, cadence, or commitments based on patterns

Time Estimate: 1-2 hours quarterly.


Tools

weekly_review_synthesizer.py

Reads structured weekly input JSON and produces a markdown weekly review.

python scripts/weekly_review_synthesizer.py input.json
python scripts/weekly_review_synthesizer.py input.json --json

Reference Guides

  • references/weekly_review_methodology.md — GTD weekly review, OKR check-in patterns, common pitfalls

Templates

  • assets/weekly_review_input.json — Input template

Best Practices

  • Block the time. 30 min recurring; defend against rescheduling.
  • Same time each week. Habits stick when the trigger is consistent.
  • Capture the pattern, not the noise. Weekly review is a layer above the moment-to-moment task list.
  • OKR check-in over chase. Weekly OKR progress is signal; quarterly is the action moment.
  • Compound across weeks. Reviews are most useful when read in batches.
  • Don't over-format. A messy review you actually do beats a perfect one you skip.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9622026년 10월 7일 업데이트

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9622026년 10월 7일 업데이트

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9622026년 10월 7일 업데이트

Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9622026년 10월 7일 업데이트

Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9622026년 10월 7일 업데이트

aeo

무료

Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9622026년 10월 7일 업데이트

borghei의 스킬 모두 보기

이 스킬의 문제 신고