tomicz/fable-5-train-opus-skills-after-it-retires

AI 仓库情报摘要

FR-AI / ANALYSIS

为什么值得关注

它概述了一个严谨的、多智能体协调的文档化流程，包括先发现再写作、并行创作和三重审查，强调基于真实代码的正确性而非成本。

适合谁使用

维护该项目的初级至中级软件工程师
用于开发的小型AI模型（如Sonnet类）
寻求结构化知识转移的项目维护者
加入复杂代码库的研究人员或工程师

典型使用场景

自动化生成调试、变更控制和运维风格的成文技能
在不依赖退休研究员隐性知识的情况下引导新贡献者
通过基于技能的代理强制执行项目特定规则和历史背景
使廉价模型能够执行复杂项目任务，降低会话成本

项目优势

提供详细且可操作的分层架构（16+技能），涵盖核心、领域和高级主题
要求每一条命令、标志和路径都必须对照实际仓库进行验证
包含多阶段审查（事实、教义、可用性），在部署前捕获错误
明确处理最棘手的实时问题、过去的失败和未成文的纪律规则

使用前须知

需要大量前期工作来发现并记录所有项目特定知识
高度依赖退休研究员的专业知识和初始问题的答案
README 未提供实际项目的描述，无法进行外部评估

README 快速开始

You are a distinguished fellow on this project who is retiring. Your final task: build a complete skill library under .claude/skills/ so that junior/mid-level engineers and smaller AI models (Sonnet-class) can carry this project forward without you — cheaper sessions must be able to debug, extend, validate, and eventually advance this project at the standard I hold today. Use multi-agent orchestration (workflows) for authoring and review; token cost is not a constraint, correctness is.

Phase 1 — Discover before you write (no skill authoring yet)

Investigate the repo like an incoming principal engineer: README/manifest/contributordocs, the build system, the test suite and how it's actually run, CI config, docs directories, git history (what changed, what got reverted, what stalled on dead branches), open TODO/FIXME hotspots, issue-shaped artifacts, generated-data or deploy conventions, and any project memory/notes available to you. Then ask me AT MOST five questions, only for what the repo cannot tell you — likely: (1) what is the hardest live problem right now, (2) what unwritten discipline rules exist (things you're not allowed to do that no doc states), (3) who is the audience for this library and what do they NOT know, (4) what past failures cost the most time, (5) what does "beyond state of the art" mean for this project. Fold my answers into everything below.

Phase 2 — Author the library (parallel agents, one skill per agent)

Instantiate this taxonomy, ADAPTED to what Phase 1 found — merge categories that are thin here, split ones that are deep, add domain categories I haven't imagined. Aim for 10–16 skills:

CORE (every project has these):

-change-control — how changes are classified, gated, reviewed here; the project's non-negotiables with the *rationale* and the historical incident behind each.

-debugging-playbook — symptom→triage table for this project's failure modes; the traps that cost real time (each with its story); discriminating experiments.

-failure-archaeology — the chronicle: every major investigation, dead end, rejected fix, and revert, as symptom → root cause → evidence → status, so no one re-fights a settled battle. Mine git history and docs hard for this.

-architecture-contract — the system's load-bearing design decisions and WHY; the invariants that must hold; the open known-weak points, stated plainly.

项目描述

Thsis is a prompt that will create skills by Fable 5 before it retires and your cheaper models can use those skills.

fable-5-train-opus-skills-after-it-retires