agentleFS
Sign inStart free
daikubo-jbdaikubo-jb/my-claude-harness/skills/feature/SKILL.md

feature

Skill0 starsChanged 2 months agoMITView on GitHub

完了条件は書けているが実装方針が1本に決まっていない依頼を、計画 → 実装 → 検証 → 記録 まで通す

71 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use bug, bugfix 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.
  • paulocsbSkill

    bug

    Investigation playbook for fixing a bug. Walks through 5 phases: reproduce → isolate → root cause → propose fix → validate. Forces concrete reasoning with code reads, log inspection, and git blame instead of pattern-matching guesses. Use for any non-trivial defect.

    Also in 8 projects that use this

  • team-attentionSkill

    bugfix

    Root cause based one-shot bug fix. debugger diagnosis → requirements.md generation → /execute. /bugfix "error description" Full investigation pipeline: debugger + gap-analyzer + standard verify. QA suggestion after successful fix.

    Also in 7 projects that use this

  • codebycoreySkill

    adopt

    Adopt an existing plan from conversation context into delta-spec format. Use when importing a plan, adopting planning that already happened, capturing plan mode output, or bringing in prior design work.

    Also in 4 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    Also in 10 projects that use this

  • marylinSkill

    recover

    Recover work from a crashed or interrupted session. Use when Claude crashed mid-task, after an unexpected exit, when you see 'stale sessions detected', or when you lost context and need to figure out what was happening.

    Also in 3 projects that use this

  • aegiswizardSkill

    context

    Also in 4 projects that use this

The file

Create a free account to mount
Files
SKILL.md

$ARGUMENTS

このセッションは sonnet で回す想定。設計から詰め直すなら skill: spec へ戻る。

完了条件を「検証可能な1文」で書けることが前提。 書けないならここに入らず、 書けるところまで聞くか skill: spec へ。

  1. 完了条件を確定して提示する。 検証方法は .claude/skills/run-*/ か プロジェクトの CLAUDE.md から取る。無ければ /run-skill-generator で先に記録させる。 自分から起動したときは、実装に入る前にこの1文を示して合意を取る
  2. 探索する。 読む範囲が広いなら Explore に投げる
  3. 実装 ⇄ 検証。 自分で書く。サブエージェントには投げない。 途中の分岐（plan-reviewer / advisor / 停止）は共通ルールの表に従う。ここには書かない
  4. 完了条件が通ったら test-runner。 アプリの挙動が変わるなら /run で実際に動かして確かめる
  5. 指摘 → 修正 → 影響する検証だけ再実行。 全部は回し直さない
  6. 記録する。 長時間・高リスク・引き継ぎのいずれかなら doc-writer に渡す。 「何を・なぜ・どう変えたか」の要約と、**「ハーネスへの示唆」**を添える

放置して自走させるなら、完了条件を提示してユーザーに /goal <完了条件> を打ってもらう。

サブエージェントにはこの会話が見えない。 仕事に必要な文脈はプロンプトに含めて渡す。

作業中にハーネス（~/.claude）を書き換えない。 気付いたことは「ハーネスへの示唆」に書くだけにして、変更は skill: harness-review で行う。

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