admin
c30430c530
gates / gates (push) Failing after 15s
The four existing skills cover the product; nothing covered how work is reported. Two rules this project has paid for — check the artifact rather than the report, and do not state a claim more firmly than the evidence allows — lived only in the operator's head and in chat, where Claude Code never read them. - felhom-evidence five confidence tiers, artifact-over-report - felhom-diagnosis no hypothesis until a command has been seen red - felhom-plain-language ASD-STE100, two options, the re-pitch - felhom-handoff the note goes to a FILE, not the conversation - felhom-doc-authoring the pointer decides whether material is reached scripts/check_skills.py asserts what decides whether a skill is EVER reached: frontmatter parses, name == directory, description and body non-empty, under 150 lines, installed copy still samefile()s into the repo. install_skills.py globs and never reads the file, so a missing description installs perfectly and then silently never loads. It convicted on its first run: felhom-build-deploy is 179 lines. NOT trimmed here (pre-existing skills are out of scope, and trimming a deploy skill without exercising its commands is how a wrong command reaches a live host) — a named single-entry GRANDFATHERED exception, WARNed every run, R-394. A new skill over the limit is convicted. Red-proof run and seen failing: description removed from felhom-evidence -> exit 1, "frontmatter field 'description' is missing or empty". Restored, tree clean. skills/SOURCES.md records both MIT upstreams, that these are adaptations not copies, and the six pieces deliberately EXCLUDED with reasons. Register: R-392 (no architecture doc covers the two-AI workflow), R-393 (decision-log skill deferred, with the reason), R-394.
2.8 KiB
2.8 KiB
Where the Felhom skills came from
The four product-domain skills — felhom-app-catalog, felhom-build-deploy, felhom-testing,
felhom-ui-design — are original, written from this project's own measured failures.
The five process-domain skills added 2026-08-25 are adaptations, not copies, of material from two public MIT-licensed collections:
mattpocock/skills— MIT.backnotprop/pstack— MIT.
Neither repo is installed, vendored, or depended on. Nothing was copied verbatim. Each skill was
rewritten in Felhom's own terms, in the house frontmatter shape taken from
skills/felhom-testing/SKILL.md, and every rule that already had a home elsewhere in this workspace
points at that home instead of restating it.
| Skill | Derives from |
|---|---|
felhom-evidence |
the confidence-grading and verify-the-artifact material in both collections, merged with this workspace's own standing rules 2 and 3 (documentation/runbooks/workspace-CLAUDE.md) |
felhom-diagnosis |
the loop-first debugging material in both collections |
felhom-plain-language |
the half of the writing guidance that cuts empty and promotional words; the ASD-STE100 rule and the two-option decision format are Felhom's own |
felhom-handoff |
the session pause/resume material in backnotprop/pstack |
felhom-doc-authoring |
the instruction-authoring material in both collections |
Deliberately excluded — a decision, not an oversight
Recorded here so a future session that finds the upstream repos can see these were weighed.
- "Stop asking and proceed on reversible work." It reasons from code is cheap and revertible. Felhom's work reaches live hosts and one real customer's data, where that premise is false, and it contradicts the standing rule that decisions go to the operator as ranked options.
- "Add voice, vary rhythm, let some mess in." The direct opposite of the ASD-STE100 rule that
felhom-plain-languageexists to carry. The empty-word-cutting half of that same upstream material was kept. - A router or "mode" skill that picks a playbook and owns the session. It takes over the
process, and would fight the
TASK-*.md/RUNBOOK-*.mdworkflow already in use. - Ticket, triage, spec-publishing and issue-tracker skills.
documentation/backlog/OPEN-ITEMS.mdis the single source of truth for open work; a skill that writes work items anywhere else creates a second one. - A codebase-architecture-survey skill. It hands back a list of things it judges wrong without knowing which were chosen deliberately, and this project has already paid four times for a deliberate design being reported as a defect.
- Everything naming a tool this project does not use — Cursor commands and transcript paths, model names, Linear / Sentry / Notion / Slack sources, GitHub issue trackers.