agentleFS
victordelrosalvictordelrosal/chairman/.claude/skills/retro/SKILL.md

retro

Skill0 starsChanged 8 months agoMITView on GitHub

Friday retrospective and next week planning. Collects wins, lessons, unresolved issues. Looks ahead at deadlines and opportunities. Drafts next week priorities. Octopus colors: Purple (synthesis) + Yellow (forward intelligence).

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-tune, ios-clean 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.
  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 9 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 11 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • +1 more from Saqlain-811
  • +2 more from ShreyRavi

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read all reports from .chairman/reports/ dated this week

    line 15
  2. Very specific:

    Read completed assignments from .chairman/assignments/

    line 16
  3. Distinctive:

    Keep it honest. Include failures and surprises, not just wins.

    line 65
  4. Very specific:

    Update .chairman/state.json with week-end status.

    line 68
  5. Very specific:

    If any lessons should become permanent knowledge, run /knowledge next.

    line 69

“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/retro: Friday Retrospective and Next Week Plan

Octopus Colors: Purple (Manager) + Yellow (Researcher)

Process

  1. Collect the week's results (Purple):
    • Read all reports from .chairman/reports/ dated this week
    • Read completed assignments from .chairman/assignments/
    • Identify: what shipped, what was learned, what broke, what surprised
  2. Compile wins (for morale and marketing potential)
  3. Compile lessons (for knowledge base)
  4. List unresolved issues (carry forward to next week)
  5. Look ahead (Yellow):
    • Upcoming deadlines or commitments
    • Scheduled meetings or events
    • Pipeline stage changes (deals advancing or stalling)
    • Seasonal or market patterns
  6. Draft next week priorities (Purple):
    • Top 3 objectives
    • Department assignments
    • Approval gates the Chairman should expect

Output Format

# Week in Review: [Date Range]

## Wins
- [What went well, with specifics]

## Lessons Learned
- [What we learned, what to do differently]

## Unresolved
- [Carried forward to next week]

## Next Week: [Date Range]

### Top 3 Priorities
1. [Priority]: [Which department, what outcome expected]
2. [Priority]: [Which department, what outcome expected]
3. [Priority]: [Which department, what outcome expected]

### Upcoming
- [Deadlines, meetings, events]

### Expected Approval Gates
- [What the Chairman will need to review/decide]

## Chairman Action
[ ] Approve priorities as-is
[ ] Adjust priorities: ___
[ ] Add priority: ___

Rules

  • Keep it honest. Include failures and surprises, not just wins.
  • Lessons should be actionable, not vague ("improve communication" is useless; "add approval gate for external content" is useful).
  • Save to .chairman/reports/retro-YYYY-MM-DD.md
  • Update .chairman/state.json with week-end status.
  • If any lessons should become permanent knowledge, run /knowledge next.

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.