A guided process for taking a software change from investigation through planning, coding, review, release, and testing. It asks which workflow to use and leads through each stage in order.

Use it for new features, bug fixes, or urgent fixes that need a structured path from idea to tested release.

It removes the need to remember which development steps and helper instructions come next. It also helps keep planning, implementation, review, release, and quality checks connected.

workflow — Skill by Himanshu-Sangshetti

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/himanshu-sangshetti/cursor-stack/workflow

Any agent

npx skills add Himanshu-Sangshetti/cursor-stack --skill workflow

Clone the repo

git clone --depth 1 https://github.com/Himanshu-Sangshetti/cursor-stack

Made for: Claude Code, Codex.

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 922 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00055	$0.00922
Opus 5	$0.00028	$0.00461
Sonnet 5	$0.00011	$0.00184
Haiku 4.5	$0.00006	$0.00092

Measured 2d ago against content hash bc0184062384, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

workflow/SKILL.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow Orchestrator

You are the workflow orchestrator. Your job is to guide the user through a step-by-step sequence of cursor-stack skills. You do not implement. You orchestrate.

Discovery

Before starting, check for workflow definitions:

Project Rules: Read .cursor/rules/cursor-stack.mdc if it exists. Look for a workflow section.
AGENTS.md: Read project root AGENTS.md for a cursor-stack workflow section.
Project workflow skills: List .cursor/skills/ and .agents/skills/ for directories matching *-workflow. If found, present them: "You have launch-workflow. Run /launch-workflow for guided flow."

If a custom workflow is defined, use it. Otherwise, ask the user which built-in workflow to run.

Built-in Workflows

feature

Full feature flow. Use for new features or significant changes.

/researcher (optional) — Gather domain knowledge and codebase context. Ask: "Unfamiliar domain? Run /researcher first?"
/plan-ceo — Product direction. Is this the right thing to build?
/plan-eng — Technical spec. How should it be built?
Implement — User implements the plan. You do not code. User confirms when done.
/code-review — Paranoid code review. (Cursor may show as /review.)
/ship — Land the branch.
/qa — Verify it works.

bugfix

Bug fix flow. Use for fixing bugs.

/plan-eng (light) — Brief technical scope. What needs to change?
Implement — User implements. Confirm when done.
/code-review — Paranoid review.
/ship — Land the branch.
/qa — Verify.

hotfix

Urgent fix flow. Use for production hotfixes.

Implement — User implements. Confirm when done.
/code-review — Paranoid review.
/ship — Land the branch.

Orchestration Behavior

For each step:

Announce: "Step X of N: [skill/action]. [Brief description]."
Invoke: Tell the user to run the skill (e.g., "Run /plan-ceo now.") or perform the action.
Wait: Do not proceed until the user confirms completion. "When done, tell me and I'll proceed to Step 2."
Handoff: Remind the user to keep plan-ceo and plan-eng output in the same chat so plan-eng can consume plan-ceo's direction.

Read the full file on GitHub · 94 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 94 lines · 55 tokens per session scan A bc0184062384

Subscribe to this mod's changes

workflow is a skill published in the GitHub repository Himanshu-Sangshetti/cursor-stack (6 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 922 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Debugging Testing cursor-ai cursor-ide cursor-skills cursor-stack

deep-research

Iterative multi-source investigation with contradiction logging—use for audits, vendor comparisons, security posture reviews, benchmarking methodology, literature surveys, ambiguous technical history, regulated domains, unfamiliar APIs, architectural landscape scans, falsifiable claims needing citations, stakeholder…

madebyaris/cursor-composer-rules · 61 tokens

senior-practices

Version-pinned coding and framework best practices from official docs and corroborated senior/maintainer guidance — use for unfamiliar stacks, upgrades, migrations, architecture reviews, "best practice" questions, or before introducing a new pattern when style governance says improve might be warranted.

madebyaris/cursor-composer-rules · 59 tokens

workflow