Matt Alton
Community@matthewalton · London, United Kingdom
Matthew Alton's Speccle skills govern feature development through spec drafting, criterion-by-criterion implementation, mutation testing, and convention-driven code review.
Agent Skills by Matt Alton
Showing 9 vetted skills indexed across 1 GitHub repositories.
matthewaltonspec-feature
Drafts and lints feature specification markdown contracts with acceptance criteria.
matthewaltonstrengthen
Evaluates per-criterion mutation testing heatmaps and routes surviving mutants to killing tests or sharper spec criteria.
matthewaltonplan-feature
Shape feature requests into ratified plans with routing, scope, and settled key decisions.
matthewaltonimplement-feature
Implements one spec criterion with token-tagged tests, a checks-gate, and a commit.
matthewaltoncarve-feature
Derive SPEC.md and CONTEXT.md contracts from existing code without changing its behavior.
matthewaltonreview
Reviews pending change sets with a lens panel and risk-gated automated fixes.
matthewaltonaddress
Fixes findings from CI-posted pull request reviews and pushes the commit to the PR branch.
matthewaltonfeature
Routes feature development through plan, spec, and implement stages driven by a deterministic CLI oracle.
matthewaltonconform
Diagnose and fix convention drift in governed feature folders after a Speccle convention change.
Frequently Asked Questions About Matt Alton
FAQPage SchemaWhat tasks can I accomplish with Matthew Alton's Speccle skills?▼
You can plan features into ratified slices, draft and lint SPEC.md acceptance criteria, implement one criterion at a time with tests-first commits, evaluate test strength via mutation heatmaps, review pending diffs with risk-scored lenses, address CI-posted PR findings, and retrofit specs onto legacy code.
Who are these skills designed for?▼
Software engineers practicing spec-driven, test-first development who want governed feature slices. They suit developers maintaining living documentation (SPEC.md, CONTEXT.md, decisions records), teams enforcing house conventions, and anyone needing structured review and remediation of pull request findings.
How do the skills run in practice?▼
Each skill is invoked by natural-language triggers like 'spec this', 'strengthen this', or 'review my changes'. The feature skill detects a slice's current stage and runs only that stage; review and address use oracle risk scoring to decide whether fixes proceed autonomously or escalate to a human.
What prerequisites do these skills require?▼
Skills read reference files under the plugin's skills directory and expect a Speccle-style repository layout with per-slice folders containing SPEC.md, CONTEXT.md, and decisions records. Implementation skills require a linted SPEC.md; conform requires an existing governed feature set and an updated convention.
Do these skills write tests or change production code?▼
It depends on the skill: spec-feature and plan-feature produce documentation only, implement-feature writes token-tagged tests and code for one criterion, carve-feature adds tests without altering existing code, and conform applies form-only fixes while keeping the test suite green throughout.