check-ticket-implement…
Check how much of a ticket is already implemented — split it into requirement blocks, judge each against the code, and save a human-readable TICKET-STATUS…
Make a project ready for AI agentic engineering by converging it toward a canonical agent-neutral structure — a lean AGENTS.md index with progressive disclosure, shared skills and gitignore hygiene. Re-runnable, and doubles as an audit.
$ npx -y skills add eai-org/agent-toolkit --skill agentify-project --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/agentify-projectContext preview
The summary Claude sees to decide when to auto-load this skill.
Make a project ready for AI agentic engineering by converging it toward a canonical agent-neutral structure — a lean AGENTS.md index with progressive disclosure, shared skills and gitignore hygiene. Re-runnable, and doubles as an audit.
name: agentify-project description: Make a project ready for AI agentic engineering by converging it toward a canonical agent-neutral structure — a lean AGENTS.md index with progressive disclosure, shared skills and gitignore hygiene. Re-runnable, and doubles as an audit. disable-model-invocation: true type: flow license: MIT metadata: version: "0.2"
Converge a project — greenfield or half-way-there — toward the canonical agent-neutral structure specified in [references/target-structure.md](references/target-structure.md) (read it before the audit), so a team of developers using different agents shares one lean, progressively disclosed setup. Re-running converges further and reports drift.
Invocation: `/agentify-project [audit] [path]`
the periodic drift check.
choice, except for obvious easy wins (e.g. clear progressive-disclosure moves). Questions answerable from the codebase go to the codebase.
happens behind the user's back. Never commit — suggest reviewing the diff and leave committing to the user.
it whenever agent detection or an agent's specifics are needed. One documented exception, the **Claude carve-out**: a team with no Claude users at all is rare, so Claude wiring (the CLAUDE.md pointer, the `.claude/skills/` links, the Claude gitignore entries) is applied unconditionally, never detection-gated.
the restructure reviewable as an isolated diff.
becomes a re-sync menu item — the one artifact class guaranteed to drift.
leave. Flag `.claude/rules/` content as candidate governing-doc material (path-scoped rules are a Claude-specific disclosure mechanism); legacy commands may get a one-off note that they could become skills — the conversion itself is out of scope.
`/context-checkup` later.
Done when every target-structure area has a detected state and every agent trace found is accounted for.
Multi-select over the applicable change areas only — entry-file indirection, AGENTS.md slimming into docs, skills relocation + symlinks, gitignore hygiene, planning dir, onboarding doc, README pointer — each annotated with audit findings (e.g. "CLAUDE.md, 180 lines, no AGENTS.md → indirection + slimming"). **"All" is the first and recommended option.** Report already-converged areas ✓ and omit them from the choices. Every area is independently skippable: a team may deliberately stay Claude-only (no multi-agent support) — then apply the selected areas within the Claude-only variant in target-structure.md.
Apply each accepted area immediately, behind its approval gate — no migration-plan artifact: the moves are mostly mechanical, and re-running converges. Suggested order: entry files → slimming/docs → skills → gitignore → extras.
**Entry files.** Invariant covering every starting state: the content of **all** existing entry files — any agent's, including a divergent CLAUDE.md + AGENTS.md pair — feeds the slimming mapping; AGENTS.md ends canonical; every detected entry file ends as a pointer (or duplicated content, per matrix), CLAUDE.md always included. Common case (CLAUDE.md exists, no AGENTS.md): rename it to AGENTS.md — git detects the rename — and recreate CLAUDE.md as `@AGENTS.md` plus any genuinely Claude-specific remainder. AGENTS.md-only and third-party-only repos: same invariant — create the missing pointer(s), seed AGENTS.md from whatever entry-file content exists. Greenfield (no entry file of any agent): minimal seed from cheap reconnaissance (README, package manifest / build files) — one-liner, **verified** build/test/run commands, planning-dir convention — plus the pointer; deep doc generation is out of scope, the structure grows later via `/self-improve` and `/memory-doctor`.
**Slimming (mapping-first).** Draft one full mapping: each block → stays / moves to existing doc X / new doc Y, applying the keep-vs-extract test (target-structure §1); where a block's relevance is verifiable from the codebase, check the code instead of asking. Present the mapping with obvious calls pre-decided; walk **only doubtful blocks** as individual questions, each with a recommendation, worded via `explain-in-simple-language` when available; one approval gate before any edit. Offer a compaction pass on blocks that stay; write extracted docs compact from birth — via `compact-docs-writer` when installed, else inline with its core principle (least text, zero information loss). Each extracted doc gets a plain-link index entry in AGENTS.md with its "read when…" hook.
**Skills.** Move real dirs, create relative symlinks (committed), per matrix; leave foreign/personal links untouched and report them.
**Gitignore.** Show the proposed block as a diff; apply on approval.
**Extras.** Planning dir + AGENTS.md convention line; onboarding doc; README pointer.
Done when every selected area is applied or explicitly skipped by the user.
Every AGENTS.md reference resolves; symli
A collection of generic agentic tools for common engineering tasks, designed to work with any AI agent on any kind of software project.
Check how much of a ticket is already implemented — split it into requirement blocks, judge each against the code, and save a human-readable TICKET-STATUS…
Draft, rewrite, or refine a doc for maximum token economy without losing any rule or intent. Use for docs kept in version control and regularly re-read by…
Author or refine a skill for maximum token economy without losing intent. Use when creating any new skill or editing an existing `SKILL.md`.
Audit what auto-loads into an agent session's context window and suggest lean, reversible fixes to cut startup tokens.
Turn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what".…
Turn a ticket or requirements document into a concise QA manual-test file a non-author can follow. Invoke manually only.