Version: 1.0 Date: 2026-09-16 Status: Shipped as TFP-051 — skills/.claude-plugin/plugin.json + a local marketplace + a committed .claude/settings.json make every skill under skills/testing/ and skills/engineering/ a real, auto-discovered Claude Code plugin skill, confirmed present on disk and described as fixed in skills/ROADMAP.md’s own Known-gaps section. This doc’s header was never updated when it landed. Corrected 2026-09-23 (Cowork verification pass).
skills/ROADMAP.md’s “Known gaps” section has flagged this since Phase
17 and it was never picked up: write-playwright-test (and now the other
ten) live under a bare top-level skills/ directory, which Claude Code’s
own skill-discovery mechanism does not scan. Every skill built across
Phases 17-20 is real, tested content — but none of it is actually
invocable as a Claude Code skill today. Right now “running a skill” in
this repo has meant a person or an agent manually opening the SKILL.md
file and following it, which works but isn’t what any of this was built
for.
This matters concretely for Phase 19: TFP-041 asks Claude Code to run
write-playwright-test directly against test-assist “with no TestForge
app involved — skill judgment in isolation.” If that only means “read the
file and follow it,” the exercise doesn’t actually test whether the skill
works the way REIMAGINING.md originally proposed using it — invoked, not
read.
Findings, checked directly before drafting this (Claude Code’s own documentation, not assumed):
.claude/skills/<name>/SKILL.md (project scope) and
~/.claude/skills/<name>/SKILL.md (user scope). A bare top-level
skills/ folder is not one of them, confirming the gap as recorded..claude-plugin/plugin.json), which can
declare a "skills" field pointing at a custom path rather than
requiring the files to live at the plugin root."skills" field accepts more than one path (needed here, since this
repo deliberately splits skills/testing/ from skills/engineering/
per the Phase 18 taxonomy decision) — or whether that split means two
plugins, or one plugin with two declared paths. Docs referenced didn’t
settle this; TFP-051 resolves it as its first step rather than guessing..claude/skills/<name> to files elsewhere in the repo is
explicitly undocumented/unsupported — not the path to take, even though
it would technically avoid restructuring anything.skills/testing/ and skills/engineering/
actually discoverable and invocable by Claude Code, without duplicating
or moving the canonical files (the testing/engineering split stays;
it was a deliberate Phase 18 decision).tooling, skills, blocking-tfp-041REIMAGINING.md’s original proposal was never
actually finished, only the content was.https://code.claude.com/docs/en/plugins-reference.md
directly (not from this ticket’s summary of it) to confirm whether
a plugin manifest’s "skills" field accepts multiple paths/an array,
or only one. This decides the shape of what follows — don’t guess.skills/testing/ and
skills/engineering/: create a single .claude-plugin/plugin.json
at the repo root declaring both paths.skills/ pointer to the parent skills/ directory
if Claude Code’s scan is recursive by category subfolder — check
which the docs actually support before picking.SKILL.md file. The manifest points at
the existing canonical locations.skills/README.md with a one-line note on how the skills are
now actually invoked (e.g. /plugin-name:write-playwright-test),
since the current README doesn’t mention invocation mechanics at all.skills/testing/ and a skill from skills/engineering/ are both
listed as available and successfully invoked through Claude Code’s
own skill-invocation path — not opened and followed manually. Paste
the actual invocation and its output as evidence, not a description.skills/ROADMAP.md’s “Known gaps” entry for this is removed (it’s
fixed, not still open).TFP-051 can run in parallel with TFP-040 (running the app doesn’t depend on skill discovery), but must finish before TFP-041 (which specifically needs real invocation, not a manual read) starts.