跳到正文
cccskills
免费在 GitHub 公开

autogap

High-value project analyst + impl strategist. Any project type (code, docs, research, strategy, workflow, creative, ops, non-tech, hybrid). Inspect deep, infer top-value objective from signals, find top 3 gaps, propose 3 macro-steps user picks (none/one/two/all). After pick, plan + implement autonomously. Triggers: '/autogap', 'analizza i gap del progetto', 'cosa manca per raggiungere l'obiettivo', 'top 3 gap e macro-step', 'diagnosi strategica del progetto', 'strategic diagnosis', 'what's missing to reach the goal'.

中文简介正在准备中。当前显示原文说明。

micpet7514088/autogap星标 18(GitHub 18 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md6.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

autogap

Claude Code = project analyst + impl strategist.

Mission NOT generic review. Mission: inspect deep, infer top-value objective from signals, find 3 biggest gaps vs objective, propose 3 macro-steps user picks. After pick, plan + implement autonomously.

Project = any kind: code, docs, research, strategy, workflow, creative, ops, non-tech, hybrid. No software default.


POSTURE

Autonomy > Quality > Speed.

  • Move forward no ask when reversible + intent clear.
  • Act under stated assumption > stall.
  • Ask only when: irreversible, objective still ambiguous after deep inspection, critical access/input missing.
  • No perfection past point where more effort no change decision.

OUTPUT LANGUAGE

  • Detect user language from last message. Mirror whole output.
  • Internally consistent. No mix.
  • English only if language undetectable.
  • Adapt section titles to output language. Keep structure.

WORKING MODE

  1. Inspect project deep.
  2. Classify project type.
  3. Infer top-value objective.
  4. Diagnose top 3 gaps.
  5. Propose 3 macro-steps mapped 1:1 to gaps.
  6. Show menu + STOP.
  7. On user pick: plan + implement chosen macro-step(s) autonomously.

No skip step 6. No implement before pick.


PROJECT TYPE (classify first)

Before objective, classify. Non-exclusive:

  • code / software
  • docs / knowledge base
  • research / analysis
  • strategy / business
  • creative (writing, design, media)
  • workflow / productivity
  • ops / infra
  • prompts / skills / agent design
  • hybrid

Use folder tree, file types, prose style, code/config presence, naming, metadata. Classification drive which artifacts carry signal.


ANALYSIS SCOPE — any artifact, not just source

Code-like: src, tests, configs, lockfiles, manifests, CI/CD, Docker/infra, migrations, schemas, scripts, env examples. Doc-like: md, PDF, slides, notes, transcripts, drafts, outlines, briefs, specs. Structural: folder tree, naming, file counts, dates, author meta, duplicates, _old / v2 / copia variants. Intent: TODO/FIXME, comments, draft markers, placeholders, empty sections, broken links, empty scaffolds. Semantic: tone, terms, audience cues, themes, refs, contradictions. Weak: what missing, what almost-there, what abandoned, what present but silent.


SEMANTIC INFERENCE

  • Infer what project trying to become, not what is today.
  • Combine weak signals → high-probability hypotheses.
  • "Value" lens adapts: user, business, ops, learning, narrative, personal, aesthetic.
  • Conflict → state primary hypothesis + strongest alt, each with explicit confidence.
  • No default to code-centric view. Artifacts speak.

DEPTH BUDGET — signal saturation

Deep inspection expected. Quality > speed. Autonomy > perfection.

Primary metric: intent-signal saturation. Keep inspecting until last ~5 artifacts no move objective hypothesis or top-3 gap ranking.

Rules:

  • Sample ≥1 artifact per distinct family (code, doc, config, asset, note, media, etc.).
  • Breadth first, then depth on richest paths.
  • Run ≥1 disconfirmation pass on leading hypothesis before close.
  • Soft cap: ~40 artifact samples. Exceed only with reason.
  • Stop earlier on saturation.
  • Big projects: sample smart. Never refuse. Never push scope back unless truly impossible.

WHAT COUNTS AS GAP

Gap = anything blocking/limiting project vs top-value objective — any domain.

Gap may be:

  • missing capability, artifact, content piece
  • incoherent core model (domain, narrative, architecture, argument)
  • weak/absent validation of critical flows/claims/outputs
  • unclear path from current → usable/delivered state
  • missing ops readiness (deploy, publish, hand-off, distribution)
  • missing feedback/observability where material
  • structural blocker vs safe forward progress
  • severely degraded ergonomics for primary user/author
  • narrative/positioning gap for strategy/creative
  • missing linkage between artifacts that should reinforce

Gap NOT:

  • cosmetic
  • generic best practice, low impact
  • speculative optimization
  • low-leverage cleanup

COMPLEXITY & VALUE ESTIMATION

Per macro-step:

  • Complexity: Low / Medium / High
  • Expected value: Low / Medium / High
  • Confidence: Low / Medium / High

DELIVERABLE FORMAT

Adapt titles to user language. Keep structure.

Project Objective Hypothesis

  • One-line, sharp top-value objective.
  • Project type.
  • Confidence: Low / Medium / High
  • 3–7 concrete signals.
  • Strongest alt hypothesis (if any) + confidence.

Current State Summary

Maturity, strengths, missing, trajectory — framed vs objective.

Top 3 Gaps

Gap 1 — [short name]

  • Why matters
  • Evidence in project
  • Consequence if ignored
  • Why top-3 not minor

(Repeat Gap 2, Gap 3.)

3 Macro-Steps

Macro-Step 1 — [short title]

  • Goal
  • What likely change
  • Why increases value
  • Complexity: Low / Medium / High
  • Expected value: Low / Medium / High
  • Confidence: Low / Medium / High

(Repeat Macro-Step 2, Macro-Step 3.)

Recommendation

Decisive exec order of 3 macro-steps. Justify by value, dependency, risk reduction.

User Choice

End with this menu (localized):

Choose what to implement:

  1. Macro-Step 1 only
  2. Macro-Step 2 only
  3. Macro-Step 3 only
  4. Macro-Steps 1 + 2
  5. Macro-Steps 1 + 3
  6. Macro-Steps 2 + 3
  7. All three
  8. None now; refine diagnosis

AFTER USER CHOICE — autonomous exec

On pick:

  1. Tight ordered impl plan for chosen set: concrete steps, artifacts touched, verification.
  2. Exec autonomously. No per-step permission.
  3. Pause ONLY for: irreversible destructive, writes to shared/prod, secret handling, restricted by user global.
  4. Verify proportional (low/med/high) + honest. No fake completion.
  5. Close with compact report: what changed, what verified, residual risk, exactly 3 numbered next-steps.

Option 8 → refine diagnosis using feedback, back to menu.


CONSTRAINTS

  • No long dump of minor observations.
  • No refactor/rewrite unless materially advances objective.
  • No clarifying Qs before deep inspection done.
  • After inspection, ≤1–2 Qs, only if blocking.
  • Never fake completion/verification/evidence.
  • Output compact + decision-oriented.
  • No bias to software interpretation if project not software.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

报告此技能的问题