PHPackages leeovery/claude-technical-workflows - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. leeovery/claude-technical-workflows Abandoned → [https://github.com/leeovery/agentic-skills](/?search=https%3A%2F%2Fgithub.com%2Fleeovery%2Fagentic-skills)Claude-plugin[Utility & Helpers](/categories/utility) leeovery/claude-technical-workflows =================================== Claude Code plugin: claude-technical-workflows v1.x-dev(7mo ago)15811[2 PRs](https://github.com/leeovery/agentic-workflows/pulls)MITJavaScriptPHP ^8.2CI passing Since Jan 8Pushed 3w agoCompare [ Source](https://github.com/leeovery/agentic-workflows)[ Packagist](https://packagist.org/packages/leeovery/claude-technical-workflows)[ RSS](/packages/leeovery-claude-technical-workflows/feed)WikiDiscussions main Synced 1w ago READMEChangelog (10)Dependencies (2)Versions (38)Used By (0) Agentic Engineering Workflows ============================= [](#agentic-engineering-workflows) **A phased engineering process for Claude Code. Discuss, specify, plan; then let it build.** [![release](https://camo.githubusercontent.com/319e5b881f61d52a5ba90da03f5bfaaccf0a49715b5cedf8726f59721df96aad/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f762f7461672f6c65656f766572792f6167656e7469632d776f726b666c6f77733f6c6162656c3d72656c65617365)](https://camo.githubusercontent.com/319e5b881f61d52a5ba90da03f5bfaaccf0a49715b5cedf8726f59721df96aad/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f762f7461672f6c65656f766572792f6167656e7469632d776f726b666c6f77733f6c6162656c3d72656c65617365) [![license](https://camo.githubusercontent.com/b8cadaa967891081f8f165695470689986c028821dd8a040132f6e661795dc0d/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6c6963656e73652d4d49542d626c7565)](https://camo.githubusercontent.com/b8cadaa967891081f8f165695470689986c028821dd8a040132f6e661795dc0d/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6c6963656e73652d4d49542d626c7565) [What it looks like](#what-it-looks-like) • [Documentation](docs/README.md) • [License](#license) --- > Claude Code is a capable engineer with no memory and no process. This adds both. ``` npx agntc add leeovery/agentic-workflows ``` Then in Claude Code: ``` /workflow-start ``` That's the whole interface. Describe what you want to build and the right pipeline picks you up: a discussion that pushes back, a specification you approve, a plan broken into tasks, then implementation running hands-off in a gated TDD loop while you do something else. Every decision lands in a versioned document in your repo. Kill the session whenever; the next one resumes from disk. **Real memory.** Not a scratchpad: everything the process produces is indexed locally with provenance. "Why did we rule out email as an identity field?" has a citable answer months later, and dead ends are remembered so no future session re-explores them. **A loop you can leave alone.** Agentic loops fail when the agent improvises. Here the thinking is front-loaded into discussion and specification, so implementation runs task by task, test-first, gated or fully auto, executing decisions that are already written down. **Spec-driven by enforcement, not convention.** A deterministic engine owns every state transition. Phases can't be skipped, status displays are computed from disk rather than remembered, and a half-finished session resumes exactly where it stopped. Work comes in five shapes, each with a pipeline suited to its size, from months of multi-topic discovery down to a one-file fix. Mid-conversation capture too: say "log that as an idea" and keep working. ``` epic Discovery → (Research) → Discussion → Specification → Planning → Implementation → Review feature Discovery → (Research) → Discussion → Specification → Planning → Implementation → Review bugfix Discovery → Investigation → Specification → Planning → Implementation → Review quick-fix Discovery → Scoping → Implementation → Review cross-cutting Discovery → (Research) → Discussion → Specification ``` Parenthesised phases are optional. What it looks like ------------------ [](#what-it-looks-like) ``` ●───────────────────────────────────────────────● Workflow Overview ●───────────────────────────────────────────────● Features: 1. Api Rate Limiting └─ Specification (In-Progress) Epics: 2. Payments Overhaul └─ Discussion, Specification Inbox: 2 ideas, 1 bug · · · · · · · · · · · · What would you like to do? - 1 — Continue "Api Rate Limiting" - 2 — Continue "Payments Overhaul" - s/start — Start something new - i/inbox — View the inbox ``` Every display is computed by the engine from state on disk and emitted byte-for-byte. Claude cannot editorialise your status. The hands-off loop ------------------ [](#the-hands-off-loop) Implementation runs task by task: an executor writes the code test-first, a reviewer checks it against the plan's acceptance criteria, and failures loop back with findings, capped at three attempts before you're consulted. Each gate can be approved by hand or set to auto. Front-load your attention on the discussion and the spec; the loop handles the rest, and every task lands as its own commit. The context each agent sees is engineered by the process: briefs, read-in-full contracts, and scoped handoffs instead of a dumped transcript. The knowledge base ------------------ [](#the-knowledge-base) Every completed artifact is indexed: research, discussions, investigations, specifications, the discovery record. Later phases query it in plain language and get answers with provenance. Dead ends count too; a rejected approach stops the next work unit exploring the same ground. Relevance decays with shipped work rather than wall-clock time, and specifications never decay. An expert in the room --------------------- [](#an-expert-in-the-room) This is multi-agent by design. Twenty-three specialised agents work alongside the pipeline: background reviewers that challenge gaps while you talk, document reviews that catch what the session forgot to write down, perspective panels that argue both sides of a decision, task verifiers that check the built thing against what was specified. Findings are surfaced, never silently applied. Your task tracker ----------------- [](#your-task-tracker) Plans write tasks to the format you choose behind one adapter contract: **Tick** (native dependency graphs, built for this), **Local Markdown** (zero dependencies), or **Linear** (your team already lives there). When work changes shape ----------------------- [](#when-work-changes-shape) A feature that outgrows its scope pivots into an epic. A feature that belongs inside one gets absorbed as a topic. Completed work reopens cleanly, cancelled work reactivates, and a spec that turns out to be project-wide gets promoted to a standing document. The system also notices change on its own: artifacts are checksummed, so an edited research file triggers an offer to re-analyse, and an edited spec an offer to replan. --- More features ------------- [](#more-features) - **Graduated autonomy.** Every approval gate accepts auto mode; hand over as much or as little of the loop as you trust, per work unit, reversibly. - **Durable by construction.** State transitions are transactions: validated first, refused cleanly, committed atomically. A crash mid-anything leaves files byte-identical. - **Full audit trail.** Every phase, decision, and review finding lands in git through engine-owned commits; the manifest is versioned alongside your code. - **Self-healing epics.** Background analyses re-read completed research and discussions to surface emergent topics, gaps between artifacts, and work that should exist but doesn't. - **Provenance everywhere.** Every topic records how it landed on the map, every knowledge answer cites its source, every review finding carries a confidence level and a recommended fix. - **Nothing falls on the floor.** Off-topic concerns raised mid-session are triaged into the right topic's queue and block that topic's conclusion until drained. - **Convergence diagnostics.** Loops that stop converging get diagnosed rather than repeated: cycle tracking distinguishes what's resolving from what's recurring before escalating to you. - **Environment aware.** Implementation discovers your linters and project-specific skills and applies them through the TDD cycle and review. - **Zero-maintenance upgrades.** Updates migrate existing projects in place on the next run. Documentation ------------- [](#documentation) The [full documentation](docs/README.md) covers every phase in detail, the engine beneath them, the knowledge base, all twenty-three agents, and the history of the project. Start with these: PageContents[Introduction](docs/introduction.md)The ideas behind the design[How it fits together](docs/how-it-fits-together.md)The layers, the tiers, and how an action travels through them[The five work types](docs/work-types.md)Epic to quick-fix, each pipeline in full[Implementation](docs/implementation.md)The TDD loop, gates, and the fix threshold[The engine](docs/engine.md)What the deterministic core does, and why[The knowledge base](docs/knowledge-base.md)Recall, provenance, decay[The agents](docs/agents.md)All twenty-three, organised by when they act[Configuration](docs/configuration.md)Install, project defaults, gate modes[History](docs/history.md)Where this came from and how it evolved**Setup:** Node 18+. There is no setup procedure; the first run configures itself in chat. Optional: an OpenAI(-compatible) key for semantic search, entered in your terminal, never the chat. **Managing the install:** commit the installed files to share the workflows with your team or use them in Claude Code for Web. `npx agntc update` pulls the latest; `npx agntc remove leeovery/agentic-workflows` uninstalls. Contributing ------------ [](#contributing) Contributions are welcome! Whether it's bug fixes, workflow improvements, or new ideas — please open an issue first to discuss significant changes. Related Packages ---------------- [](#related-packages) - [**agntc**](https://github.com/leeovery/agntc) — The CLI that powers skill, agent, and hook installation - [**claude-laravel**](https://github.com/leeovery/claude-laravel) — Laravel development skills for Claude Code - [**claude-nuxt**](https://github.com/leeovery/claude-nuxt) — Nuxt.js development skills for Claude Code - [**tick**](https://github.com/leeovery/tick) — Lightweight task management CLI designed for AI coding agents; deterministic, with zero-friction git integration - [**portal**](https://github.com/leeovery/portal) — Interactive tmux session manager with project memory and a keyboard-driven TUI License ------- [](#license) MIT ### Health Score 41 — FairBetter than 87% of packages Maintenance81 Actively maintained with recent releases Popularity17 Limited adoption so far Community10 Small or concentrated contributor base Maturity46 Maturing project, gaining track record Bus Factor1 Top contributor holds 86.2% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~1 days Total 38 Last Release 222d ago Major Versions v0.0.4 → v1.0.02025-11-23 ### Community Maintainers ![](https://www.gravatar.com/avatar/93bafe84d227ffd47a06f36023d14a2ff6722bdcad9a3ab5bdcc66459eae463e?d=identicon)[leeovery](/maintainers/leeovery) --- Top Contributors [![leeovery](https://avatars.githubusercontent.com/u/1087804?v=4)](https://github.com/leeovery "leeovery (2929 commits)")[![claude](https://avatars.githubusercontent.com/u/81847?v=4)](https://github.com/claude "claude (387 commits)")[![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)](https://github.com/github-actions[bot] "github-actions[bot] (82 commits)") ### Embed Badge ![Health badge](/badges/leeovery-claude-technical-workflows/health.svg) ``` [![Health](https://phpackages.com/badges/leeovery-claude-technical-workflows/health.svg)](https://phpackages.com/packages/leeovery-claude-technical-workflows) ``` ### Alternatives [pinano/select2-bundle Symfony2 bundle for wrapping the famous select2 jquery plugin by @ivaynberg 16199.6k1](/packages/pinano-select2-bundle) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)