devpath
v0.5.0One engineering workflow: requirement to merged code. Eight stages, two human gates, ten skills.
By Jonah StephansLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 10 skill or MCP entries
- Source updated
- Aug 28, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install plugin
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install devpath@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/Jonah-Stephans/devpathClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json├── skills/build/SKILL.md├── skills/critique/SKILL.md├── skills/fit-check/SKILL.md├── skills/initiate/SKILL.md├── skills/integrate/SKILL.md├── skills/learn/SKILL.md├── skills/sketch/SKILL.md├── skills/slice/SKILL.md├── skills/survey/SKILL.md└── skills/technical-design/SKILL.md
Included Skills10
Build the slices of an approved devpath spec into code and tests. Use once a design is approved and its slices are cut.
Critique the code of a built devpath slice. Use after a slice is built, or when a reviewer has requested changes on the spec's pull request.
Check a repo against the twenty-six preconditions devpath needs and report where it stands. Use before adopting devpath on a repo, or any time afterwards to see what is still missing.
Turn an arriving requirement — a link, a paste, or one typed sentence — into a devpath spec. Use at the start of a piece of work, before any design or code.
Check a built devpath spec against its Outcomes and release it to merge. Use when every slice of a spec is done and the work is ready to ship.
Propose codebase lessons from a finished devpath spec. Use at the end of Integrate, or point it at a pull request to capture something review turned up.
Produce something physical to settle an open design question on a devpath spec. Use when a design conversation stalls because two people picture different screens.
Cut an approved devpath design into slice files. Use to run the slice stage on its own, to re-cut a layout that was rejected, or to cut only what a reworked design adds on a spec whose slices are already built.
Find what already exists in a repo that bears on a devpath spec's Outcomes. Use when a spec is accepted and its current state is not yet known.
Run the design conversation on an accepted devpath spec. Use once a spec's intent is accepted and before any code exists.
Plugin manifests1
{
"name": "devpath",
"version": "0.5.0",
"description": "One engineering workflow: requirement to merged code. Eight stages, two human gates, ten skills.",
"author": {
"name": "Jonah Stephans",
"email": "[email protected]"
},
"repository": "https://github.com/Jonah-Stephans/devpath",
"license": "MIT",
"keywords": [
"salesforce",
"workflow",
"specs"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[devpath on Agent Plugins Marketplace](https://pluginsmp.com/plugins/devpath)