agentleFS
tohuretohure/Diccionario-Muchik/.claude/skills/speckit-plan/SKILL.md

speckit-plan

Skill0 starsChanged 6 months agoNo licenceView on GitHub

Execute the implementation planning workflow using the plan template to generate design artifacts.

134 other projects use a version of this, 124 of them edited; 104 of 122 edited versions we compared changed its rules.

How people change it

104 of 122 edited versions changed its rules, and some changes recur.

Of the 122 edited versions we compared: 13 keep every rule, 5 are an older text, 104 made changes of their own.

Not in older versions

  1. When constructing slash commands from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.missing from 5 of 5

Rules people drop

  1. Update the plan reference between the <!-- SPECKIT START --> and <!-- SPECKIT END --> markers in CLAUDE.md to point to the plan file created in step 1 (the IMPL_PLAN path)dropped by 91 of 104
  2. If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normallydropped by 36 of 104
  3. When constructing slash commands from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit → /speckit-git-commit.dropped by 11 of 104
  4. Use absolute paths for filesystem operations; use project-relative paths for references in documentation and agent context filesdropped by 10 of 104
  5. Check if .specify/extensions.yml exists in the project root.dropped by 3 of 104
  6. If it exists, read it and look for entries under the hooks.before_plan keydropped by 3 of 104
  7. If the hook has no condition field, or it is null/empty, treat the hook as executabledropped by 3 of 104
  8. If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementationdropped by 3 of 104

Rules people add

  1. Document runnable validation scenarios that prove the feature works end-to-endadded by 92 of 104
  2. Use links or references to contracts and data model details instead of duplicating themadded by 92 of 104
  3. Do not include full implementation code, model/service/controller bodies, migrations, or complete test suitesadded by 92 of 104
  4. Keep this artifact as a validation/run guide; implementation details belong in tasks.md and the implementation phaseadded by 92 of 104
  5. If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, …added by 33 of 104
  6. Update the appropriate agent-specific context fileadded by 9 of 104
  7. Add only new technology from current planadded by 9 of 104
  8. A rule we can't quote: its licence doesn't allow itadded by 2 of 104

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Most recently taken up by

Used with

Projects with it also use speckit-agent-context-update, speckit-baseline and 5 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.
  • Microsoft AzureSkill

    speckit-agent-context-update

    Refresh the managed Spec Kit section in coding agent context file(s)

    Also in 13 projects that use this

  • patterson-agentsSkill

    speckit-baseline

    Generate feature specifications by analyzing existing source code.

    Also in 3 projects that use this

  • patterson-agentsSkill

    claude-command-converter

    Convert Claude Code commands (.claude/commands/*.md) to standard Agent Skills (skills/*/SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.

    Also in 3 projects that use this

  • arkanSkill

    review-animations

    Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    agentic-workflows

    Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

    Also in 3 projects that use this

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 3 are common, 0 are distinctive, and 11 are very specific to this project.

  • 3

    Common

    Most of the 123 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 11

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.