agentleFS
Sign inStart free
Adelie-SquadAdelie-Squad/solosquad/skills/retrospective/SKILL.md

retrospective

Skill25 starsChanged 9 days agoMITView on GitHub

Cycle 종료 시 회고 진행. gstack /retro per-contributor breakdown + RO-PNA Confidence Score 갱신. Chief 가 RETROSPECT stage 에서 호출. weekly cron 에서도 호출.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dev-story, team-level and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    dev-story

    Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.

    Also in 12 projects that use this

  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 12 projects that use this

  • CoralGameSkill

    team-narrative

    Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.

    Also in 12 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • +7 more from lilangMax
  • +1 more from CoralGame

The file

Create a free account to mount
Files
SKILL.md

Retrospective Skill

Chief 가 cycle (workflow / goal / weekly) 종료 시 호출. 객관적 metric + 패턴 식별 + 액션 항목 도출.

입력

  • 종료된 workflow id / goal id / period (e.g. last 7d)
  • <org>/memory/chief-stage-events.jsonl — stage 전환 trace
  • <org>/memory/ledger/<task-id>.jsonl — task event ledger
  • <org>/memory/agent-costs.jsonl — agent 별 USD 소비
  • <org>/memory/leading-indicators.jsonl — 누적 지표

Per-Contributor Breakdown (gstack 차용)

per_contributor:
  founder:
    inputs: <N>           # 사용자 메시지 수
    decisions: <N>        # batch 답변 / explicit approval 수
  chief:
    stages_executed: <N>
    open_questions_batched: <N>
  pm:
    spawns: <N>
    design_docs_produced: <N>
    open_questions_resolved: <N>
    avg_confidence: 0-100
  engineering:          # frontend/backend/data-engineer · infra · quality-assurance 합
    prs_shipped: <N>
    test_coverage_delta: <%>
  designer:
    specs_produced: <N>
    prototypes: <N>
  marketer:
    campaigns: <N>
    content_assets: <N>

Shipping Streak

shipping_streak:
  current_days: <N>    # 연속 release / merge 일수
  best: <N>
  threshold: ">=7 stable, <7 yellow"

Confidence Score 갱신

period 내 PM 가설 confidence 평균:

avg_confidence:
  start_of_period: 0-100
  end_of_period: 0-100
  delta: <+/->
  reasoning: "string"

출력

period: "..."           # workflow id 또는 ISO 날짜 범위
metrics: { per_contributor, shipping_streak, avg_confidence }
what_worked: ["..."]
what_didn_work: ["..."]
patterns_observed: ["..."]
action_items:
  - { owner: chief|product-manager|backend-engineer|..., action: "...", target_date: "YYYY-MM-DD" }
followup_skills:
  - skill-refinement     # 호출 권고 시
  - workflow-refinement  # 호출 권고 시

Anti-Sycophancy

  • ❌ "잘 한 점이 많네요"
  • ✅ "5/7 일 ship 성공. miss 2건 모두 weekend 의존 task. Y 면 weekend 의존 task 분리 권고."

Reference

  • gstack /retro per-contributor breakdown
  • RO-PNA Confidence Score
  • v1.1 PRD §5.2 (Chief RETROSPECT stage)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free