agentleFS
Sign inStart free
kohj1018kohj1018/agentic-dev-harness/.agents/skills/validate-plan/SKILL.md

validate-plan

Skill2 starsChanged 45 days agoMITView on GitHub

Use ONLY when the user explicitly types `$validate-plan <workitem-id>`. Do not trigger implicitly from generic phrasing.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use iterate-plan, research-codebase and 4 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.
  • corticalstackSkill

    iterate-plan

    Revise an existing implementation plan in flow/plans/ based on feedback, researching when needed. Explicit-only; run only when invoked via /iterate-plan or explicitly asked.

    Also in 3 projects that use this

  • joshuaalpuertoSkill

    research-codebase

    Conducts structured research across a codebase to answer questions about architecture, components, and data flow. Use when investigating how code works, where functionality lives, or how systems interact. Decomposes questions, runs parallel investigations, synthesizes findings with file:line references, and produces persistent research documents.

    Also in 4 projects that use this

  • parcadeiSkill

    describe-pr

    Generate comprehensive PR descriptions following repository templates

    Also in 3 projects that use this

  • JasonPaffSkill

    implement-plan

    Execute implementation plan with structured tracking and validation using subagent architecture

    Also in 4 projects that use this

  • JetBrainsSkill

    create-plan

    Research the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Treat all frontmatter keys other than name and description (e.g., agent:, disable-model-invocation:, allowed-tools:, context:, …

    line 8
  2. Distinctive:

    If the source path no longer exists, this wrapper is stale — see ADR-010.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 7 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

Source of truth: .claude/skills/validate-plan/SKILL.md (skill 신설 근거: ADR-038). Read it and follow the workflow.

Treat all frontmatter keys other than name and description (e.g., agent:, disable-model-invocation:, allowed-tools:, context:, argument-hint:, model:, effort:) as Claude-only and ignore them — execute locally in Codex.

Slash command translation: 본문 안의 /validate-plan 표기는 Claude 슬래시 커맨드다. Codex에서는 $validate-plan으로 읽고 사용자에게 안내한다. 본문에 등장하는 /repair-plan 표기도 $repair-plan으로 안내. Codex CLI는 /를 빌트인 슬래시 커맨드에 쓰므로 명시적 치환이 필요.

Preserve all repo policies from AGENTS.md and docs/.

If the source path no longer exists, this wrapper is stale — see ADR-010.

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