jthorare/agentic-workflow

A portable, provider-agnostic workflow toolkit for AI coding agents. It works the same way in Claude Code, Codex, and Cursor: 53 native skills plus 3 fetched external design packs (impeccable, emil-design-eng, taste-skill), a repo bootstrapper, safety hooks, a cheap-decision judge, Sindri (the C# control plane and workflow engine), and a token-efficiency tool (the rtk command rewriter).
There is one canonical core: skills, hook logic, MCP servers, and judge. Each provider gets a thin adapter on top. Skills describe capabilities ("ask the user", "spawn a subagent", "call an MCP tool"), and each provider maps those to its own tools. See Providers and planning/PROVIDERS.md.
> New here? Start with the onboarding guide: ONBOARDING.md, or the visual walkthrough in docs/onboarding.html (open it in a browser).
> Invoking skills: the examples below use / (Claude Code, Cursor). In Codex, use $ . For example, $review instead of /review.
## Workflow: Product Vision → Ship
This toolkit supports an end-to-end product workflow where AI sessions replace documents. The goal is to make GitHub issues the single source of truth, instead of piling up local markdown files.
### Stage 1 — Ideation
/withInterview
Human in the loop: You're in the hot seat. The agent interviews you. It asks questions, challenges assumptions, and surfaces contradictions while you answer in your own words. The output is a coherent problem statement and set of goals distilled from your raw thinking. You don't have to write polished prose yourself.
### Stage 2 — Spec & Design Doc
/officeHours [feature or problem]
Human in the loop: This is a back-and-forth collaboration. The agent proposes requirements and you push back. It drafts the technical design, and you redirect priorities and flag constraints it doesn't know about. Think of it as a YC office hours session: you leave with decisions made, not just options listed. It also gives structure to multi-team collaboration. Product and engineering can align on vision, scope, and trade-offs in a shared session before anyone writes a line of code. The output lands in ~/.agentic-workflow/ /plans/ /: a canonical plan.md handoff plus per-owner docs:
| File | Owner | Contents |
| product.md | Product | Problem statement, EARS requirements, acceptance criteria, success metrics, MVP scope |
| engineering.md | Engineering | Current state, approach, architecture decisions, open questions |
| design-brief.md | Design | Experience goals, key interactions, UX requirements, design language reference |
| TASKS.md | Engineering | Atomic task breakdown with domain tags for cross-team visibility |
Each file is a standalone artifact. Everyone leaves the session with a doc they own, not a monolith that nobody owns.
You can optionally pressure-test the outputs before moving on. Run each lens on its own, or use /autoplan to run them all in parallel:
/productReview # Founder/product lens: is this the right thing to build?
/archReview # Engineering lens: is this the right way to build it?
/autoplan # productReview + archReview + planDesignReview + planDevexReview + cso(plan), in parallel
### Stage 3 — Design System & Mockups