SPARC Development Methodology
ruvnet/ruflo
Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.
Sketches types, signatures and module boundaries with stub bodies before real code, compares at least two designs, then implements against the chosen sketch.
Install Architect Before Implementing
$ npx skills add cursor/plugins --skill architect -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cursor/plugins architect --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pstack/skills/architect .claude/skills/architect && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "architect" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/architect into .claude/skills/architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architect", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cursor/plugins/tree/main/pstack/skills/architectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cursor/plugins --skill architect -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cursor/plugins architect --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pstack/skills/architect .agents/skills/architect && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architect" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/architect into .agents/skills/architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architect", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cursor/plugins --skill architect -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cursor/plugins architect --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pstack/skills/architect .cursor/skills/architect && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "architect" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/architect into .cursor/skills/architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architect", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cursor/plugins.git --path pstack/skills/architect--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cursor/plugins --skill architect -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cursor/plugins architect --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pstack/skills/architect .gemini/skills/architect && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "architect" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/architect into .gemini/skills/architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architect", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cursor/plugins architectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cursor/plugins --skill architect -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/pstack/skills/architect .github/skills/architect && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "architect" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/architect into .github/skills/architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architect", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cursor/plugins --skill architect -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cursor/plugins architect --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pstack/skills/architect .opencode/skills/architect && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "architect" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/architect into .opencode/skills/architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architect", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
architect- GitHub stars
- 10k
- Used in
- 8 other repos
- Token cost
- ~1.4k tokens
- SKILL.md length
- 781 words
- Files
- 4 (incl. references)
- Skills in repo
- 99
- Repo updated
- First seen
- Licence
- None found
At a glance
Sketches types, signatures and module boundaries with stub bodies before real code, compares at least two designs, then implements against the chosen sketch.
- Works in 5 steps: Ground → Sketch → Agree → …
- Starting non-trivial work where the shape of the code is still open
- SKILL.md covers Start, Phase A: Ground the problem, Phase B: Sketch and Phase C: Agree (opt-in), plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill puts design ahead of implementation for work where jumping straight to code would lock in the wrong shape. The agent opens a to-do list with five phases: ground, sketch, agree, implement and scrap. Grounding builds a traced model of every system the new code touches by running a companion `how` skill, plus a `why` skill when the design changes ownership or layering; only truly greenfield work may skip it.
In the sketch phase an `arena` skill runs several model runners on the problem, each returning a design package in the format of `references/rationale-template.md`, and at least two structurally different whole-shape candidates are required before synthesis. Candidates are screened against `references/design-red-flags.md`, on the assumption that the next contributor is an agent that copies the nearest example, and a smaller, deeper public interface is preferred. The agreement phase is opt-in, and implementation fills in code against the sketch; if the code shows the sketch is wrong, the sketch is discarded and redone.
When your agent uses it
- Starting non-trivial work where the shape of the code is still open
- Answering a request to architect or design a feature before any coding
- Comparing two or more module structures before committing to one
- Redefining ownership or layering between modules
Example prompts
- “Architect this: a retry layer for our outbound webhooks. Sketch types and signatures first.”
- “Design the module boundaries for the new billing sync before we write any code.”
- “Give me two structurally different designs for the notification queue, then pick one.”
Requirements
- The companion how, why and arena skills from the same plugin
- Several model runners for the sketch phase
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Ground
- Sketch
- Agree
- Implement
- Scrap
What it can do on your machine
Read from SKILL.md and the folder at commit 9f451cf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Architect Before Implementing loads about 1.4k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 781 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 781 words (~1,416 tokens).
“Design before implementing. Sketch types, function signatures, class shapes, and module boundaries with not implemented bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch. If implementation proves the sketch wrong, throw it out…”
- name
- architect
- disable-model-invocation
- true
Files
SKILL.md and 3 other files (references) in pstack/skills/architect of cursor/plugins.
- SKILL.md
- references/design-red-flags.md
- references/rationale-template.md
- references/runner-prompt.md
Open the folder on GitHubat commit 9f451cf
Used in 8 other repositories
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 8 other GitHub owners. This page covers the copy in cursor/plugins, which our catalogue first saw on October 7, 2026.
- chmonitor/chmonitor.claude/skills/pstack/upstream/skills/architect
- Sma1lboy/rove.agents/skills/pstack/skills/architect
- michael-denyer/pstack-claudeplugins/pstack/skills/architect
- backnotprop/pstackskills/architect
- tellahq/opensession.agents/skills/pstack-suite/skills/architect
- am-will/gooey-pi.agents/skills/pstack/architect
- jtaroreh/agystackskills/architect
- uzairansaruzi/p3-stackskills/architect
Compare with similar skills
Architect Before Implementing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Architect Before Implementing this skillcursor/plugins | 10k | 8 repos | ~1.4k | Automated safety check: Pass | None | |
| SPARC Development Methodologyruvnet/ruflo | 74k | 2 repos | ~829 | Automated safety check: Pass | MIT | |
| Think: Plan Before You Buildtw93/Waza | 7.2k | — | ~3k | Automated safety check: Notes | MIT | |
| SPARC Methodologyruvnet/agentic-flow | 816 | 6 repos | ~6.3k | Automated safety check: Pass | None | |
| GitHub Multi-Repo Coordinationruvnet/agentic-flow | 816 | 5 repos | ~5.6k | Automated safety check: Pass | None | |
| Engineering Plan Reviewgarrytan/gstack | 136k | — | ~13k | Automated safety check: Notes | MIT |
Similar skills
Think: Plan Before You Build
tw93/Waza
Turns a rough idea into an approved, decision-complete plan or recommendation before any code is written, for architecture choices and go or no-go calls.
SPARC Methodology
ruvnet/agentic-flow
Structures complex feature work into five planning-first phases (specification, pseudocode, architecture, refinement and completion) driven through claude-flow commands.
GitHub Multi-Repo Coordination
ruvnet/agentic-flow
Coordinates work across several GitHub repositories: swarm-driven cross-repo operations, package version and documentation sync, and repository structure optimization.
Engineering Plan Review
garrytan/gstack
Reviews an execution plan or design doc before coding, covering architecture, data flow, edge cases, test coverage and performance, one issue at a time.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
More from cursor/plugins
All 99 skills in this repo- Official
Show Me Your Work Decision Log
cursor/plugins
Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
- Official
Reflect on Session Learnings
cursor/plugins
Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
- Official
Advisor Mode
cursor/plugins
Adds a second, stronger model that the main agent consults before major decisions, when stuck and before finishing, controlled by /advisor commands.
- Official
Make PR Easy To Review
cursor/plugins
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.
Related
Categories
Questions about Architect Before Implementing
What does Architect Before Implementing do?
Sketches types, signatures and module boundaries with stub bodies before real code, compares at least two designs, then implements against the chosen sketch. This skill puts design ahead of implementation for work where jumping straight to code would lock in the wrong shape. The agent opens a to-do list with five phases: ground, sketch, agree, implement and scrap.
When should I use Architect Before Implementing?
Architect Before Implementing fits situations like: starting non-trivial work where the shape of the code is still open; answering a request to architect or design a feature before any coding; comparing two or more module structures before committing to one; redefining ownership or layering between modules.
How do I install Architect Before Implementing in Claude Code?
Run `npx skills add cursor/plugins --skill architect -a claude-code`. Or copy the skill folder (pstack/skills/architect in cursor/plugins) into .claude/skills/architect in your project. Claude Code loads it when a task matches its description.
How do I install Architect Before Implementing in Codex?
Run `npx skills add cursor/plugins --skill architect -a codex`. Or copy the skill folder (pstack/skills/architect in cursor/plugins) into .agents/skills/architect in your project. Codex loads it when a task matches its description.
Can I use Architect Before Implementing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cursor/plugins --skill architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architect, .gemini/skills/architect, .github/skills/architect and .opencode/skills/architect in your project.
What does Architect Before Implementing need to run?
SKILL.md names no scripts, command-line tools or credentials: Architect Before Implementing is instructions for the agent only. Our summary lists: The companion how, why and arena skills from the same plugin; Several model runners for the sketch phase.
Does Architect Before Implementing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architect Before Implementing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Architect Before Implementing use?
No licence was found for Architect Before Implementing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Architect Before Implementing use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.
What are the alternatives to Architect Before Implementing?
Skills that share tags, products or a category with Architect Before Implementing: SPARC Development Methodology (ruvnet/ruflo, 74k stars), Think: Plan Before You Build (tw93/Waza, 7.2k stars), SPARC Methodology (ruvnet/agentic-flow, 816 stars) and GitHub Multi-Repo Coordination (ruvnet/agentic-flow, 816 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architect Before Implementing?
cursor (a GitHub organization, an official publisher) maintains it in cursor/plugins, which has 10,130 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 6, 2026.
Source: cursor/plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.