project-lifecycle

النجوم١٠

التفرعات٠

آخر تحديث٢٩ يوليو ٢٠٢٦ في ٠٦:٣٧

Bootstrap, organize, or archive project tracking docs. Use when: "archive this project", "bootstrap from plan", "set up project tracking", "clean up project docs", "update INDEX", "reorganize docs/projects/", "歸檔這個專案", "建專案", "整理專案文件", project is done and merged — needs cleanup. Not for: authoring a plan doc (→ references/plan-template.md), choosing what to work on (→ next), or running quality gates (→ quality-pipeline).

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

cookys

cookys/autopilot

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

متخصصو إدارة المشاريعمهن الأعمال والعمليات المالية·SOC 13-1082

مستكشف الملفات

5 ملفات

SKILL.md

readonly

name

project-lifecycle

description

Project Lifecycle

Project Config (auto-injected)

!cat .claude/project-lifecycle-config.md 2>/dev/null || true

Phase	Reference	When
Bootstrap	references/plan-bootstrap.md	After plan approval for L-size projects
Structure	references/project-structure.md	Creating project dirs, organizing docs
Archive	references/project-archive.md	Finishing a development branch, user says "archive"

المزيد من هذا المستودع

نفس المستودع

quality-pipeline

cookys/autopilot

Run pre-commit or pre-merge quality checks: tests, completeness scan (no stubs/TODOs/mocks), code review. Use when: "quality gate", "quality checks", "run tests before merge", "check for stubs", "scan for completeness", "is this ready to commit?", "pre-merge review", "品質檢查", "準備好可以 commit 了嗎", "跑一下檢查". Not for: writing new tests (→ TDD), debugging CI failures, or receiving external review feedback.

2026-07-3110

cookys/autopilot

Terse CEO front-door — Level 6: like /l5 (worktree-isolated hetero implementer + authoritative qc) but the VERIFICATION AUTHORING is also leaf-dispatched to a heterogeneous engine; depth-0 remains pure orchestration. Use when: "/l6 <goal>", "L6 <goal>", "全委", "全部派遣", "省 token 全外包", "delegate everything incl verification". Presets involvement=just-results, scope=Hold, project red lines plus -x additions (override --mode / --expand / --solo). Not for: /l5 when you still want to do verification yourself; /l4 all-Claude; /l3 inline.

2026-07-2910

finish-flow

cookys/autopilot

Closing sequence forcing function — use at the END of any dev-flow workflow (L, H, Fix, S) to guarantee no step in the closing sequence gets silently compressed or skipped. On invocation, creates size-appropriate sub-tasks via TaskCreate so each step is individually trackable. MANDATORY for L-size (invoked at L-5) and H-size (invoked at step 9); optional for Fix/S. Use when: finishing L-size project, closing hotfix, "time to merge", "wrap this up", "跑完收尾", "收掉這個專案", "L-5 開始". Not for: mid-phase work, starting new work (→ dev-flow), authoring a plan doc (→ references/plan-template.md).

2026-07-2910

retro

cookys/autopilot

Engineering retrospective from git history — velocity, test ratio, focus score, commit patterns. Use when: "/retro", "retro on last N days", "how productive was this sprint", "analyze my commit history", "work patterns", "session analysis", "回顧", "分析工作模式", "這週做了什麼". Not for: viewing specific commit diffs, comparison audits, or debugging test coverage drops.

2026-07-2810

research-to-ship

cookys/autopilot

Pinned participatory pipeline — research industry best-practice → write a plan → bounded, rubric-frozen plan review (maximum two generations) → expand into a tracked project → execute per dev-flow. Each phase ends at a human approval gate. Use when: "research best practice on X then build it properly", "查業界 best practice 寫成 plan、有限 review 後展開成 project 照 dev-flow 跑", "把這個主題做成正式專案", "spec it out then ship it the rigorous way". Not for: full hands-off autonomy (→ ceo-agent), a quick fix / already-known implementation (→ dev-flow), research with no build (→ survey / deep-research), or a single irreversible decision (→ think-tank-dialectic).

2026-07-2810

dev-flow

cookys/autopilot

Start here before writing any code — sizes task (S/L/H/Fix), sets up branch and session rules. Use when: "I'm starting on X", "quick fix for Y", "continuing from yesterday", "hotfix needed", "let's implement X", "skip to coding", "我要開始做 X", "快速修一下", "接續昨天的進度", resuming a feature branch, or any task that touches code. Not for: debugging (→ debug), authoring a plan doc (→ references/plan-template.md), pre-code design exploration (→ brainstorm), or code review (→ quality-pipeline).

2026-07-2810