Ray Amjad's skills plugin
Skills from an idea to proven results: a spec, building and verifying a PR and a verification skill for your app.
- 66 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The `/task-lifecycle` skill edits code, runs the app and opens a pull request.
- The verification skill drives the real app.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/ray-amjad-s-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The `/task-lifecycle` skill edits code, runs the app and opens a pull request.
- The verification skill drives the real app.
This is third-party code. Review the repository files before installing.
What it does
The set drives a change along a chain. `/idea-to-spec` turns a rough idea into a short spec with goals, constraints and a Proof section where every line is backed by the author's decision. `/task-lifecycle` builds the change into a verified pull request: one builder, independent review and fix rounds, then a verify step on the live app. The skill asks you before merging. The Prove It group has `/create-prove-it`, `/maintain-prove-it` and `/audit-prove-it`. The first creates the repository's own verification skill `/prove-<app>`, the second keeps it current and the third plants bugs and checks that the verification catches them. The spec's Proof section serves as the answer key, and the builder fixes the app but never the key.
Who it is for. Developers who hand whole changes to an agent and want proof that they work.
Good fit when
- A rough idea is fixed in a spec with verification criteria before building.
- A change passes a builder, an independent review and a check on the running app.
- A repository gets its own verification skill that the agent runs after every edit.
- Verification quality is tested with planted bugs.
Not a fit when
- You need one edit without a spec and rounds.
- The app cannot be run or checked automatically.
- You do not want the skill to create a pull request.
Example request
Use idea-to-spec for the CSV export idea, then build it with task-lifecycle and show verification on the live app.Limitations
Prove It is in beta and still changing, so behaviour may shift between releases. `/task-lifecycle` drives the real app and opens a pull request, so give the agent a separate branch and a safe environment. The skill asks before merging but does not replace your access control. Install is described for Claude Code, Codex and any agent through `npx skills`, under the MIT licence. It works with agents that read `SKILL.md` files. For verification to be meaningful the spec Proof section needs observable criteria, otherwise `/prove-<app>` has nothing to compare against.
How to disable. Remove the plugin with the Claude Code or Codex command, or the skill folders from `~/.claude/skills/` and `~/.agents/skills/`. Delete the generated `/prove-<app>` skill from the repository.
FAQ
How do I install it in Codex?
Run `codex plugin marketplace add ray-amjad/skills` and `codex plugin add ray-amjad-skills@ray-amjad`.
How do I install it in another agent?
With `npx skills@latest add ray-amjad/skills` or by copying folders from `skills/` into `~/.claude/skills/` or `~/.agents/skills/`.
What is the Proof section in the spec?
The answer key. `/task-lifecycle` builds to it, and its verify step runs your repository's `/prove-<app>` when there is one.
What does /audit-prove-it do?
It plants bugs in the app and checks that your verification skill finds them.
Does the skill ask before merging?
Yes, `/task-lifecycle` asks for your decision before merging the pull request.
Discussion
No questions or reviews yet.
Related
PluginsSkills for spec-driven development: brainstorming, planning, debate-style review and idea grilling before the first commit.
An evidence-first development skill: the agent wraps code in a spec and a gauntlet of checks so line-by-line review becomes optional
Six linked skills take a project from a raw idea to a validated build plan and a first draft in Claude Code and Codex.
Skills for Claude Code and other agents: spec pushback, six-specialist branch review, architecture and accessibility audits
Nine JS Mastery skills take a change through phases: from idea and spec to verification, tests, release texts and a docs sync
A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
README in short
The skills form a chain: spec, build and review, verification. The Prove It section is described separately in the README and marked beta.