Skip to content
Agentmart
Submit a tool

engineering-rigor

Rigorous agentic engineering workflow — 23 playbooks and 23 principle rules for bug fixes, features, refactors, performance work, investigations, architecture…

Skill by harryhecanada

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/harryhecanada-engineering-rigor

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Rigorous agentic engineering workflow — 23 playbooks and 23 principle rules for bug fixes, features, refactors, performance work, investigations, architecture decisions, code review, and long autonomous runs. Use for any non-trivial engineering task, or when the user asks for rigor, anti-slop discipline, verified work, or a plan they can audit. Also use when work must be proven against real runtime evidence rather than declared done.

Use cases: security, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/engineering-rigor

What's inside

Skill name
engineering-rigor
Description
Rigorous agentic engineering workflow — 23 playbooks and 23 principle rules for bug fixes, features, refactors, performance work, investigations, architecture decisions, code review, and long autonomous runs. Use for any non-trivial engineering task, or when the user asks for rigor, anti-slop discipline, verified work, or a plan they can audit. Also use when work must be proven against real runtime evidence rather than declared done.
License
MIT
Instructions
86 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (141)

  • LICENSE
  • README.md
  • SKILL.md
  • TOOLS.md
  • comment-sicko.md · agents/
  • poteto-agent.md · agents/
  • AGENTS.md · rules/
  • models.md · rules/
  • gate-delegation.sh · scripts/
  • gate-safety.sh · scripts/
  • SKILL.md · skills/architect/
  • design-red-flags.md · skills/architect/references/
  • rationale-template.md · skills/architect/references/
  • runner-prompt.md · skills/architect/references/
  • SKILL.md · skills/arena/
  • SKILL.md · skills/automate-me/
  • SKILL.md · skills/blast-radius/
  • SKILL.md · skills/bro/
  • SKILL.md · skills/create-verification-skill/
  • README.md · skills/create-verification-skill/references/feature-map-example/
  • create-note.md · skills/create-verification-skill/references/feature-map-example/
  • search.md · skills/create-verification-skill/references/feature-map-example/
  • SKILL.md · skills/deslop/
  • SKILL.md · skills/figure-it-out/
  • SKILL.md · skills/how/
  • explainer-prompt.md · skills/how/references/
  • explorer-prompt.md · skills/how/references/
  • SKILL.md · skills/interrogate/
  • code-quality-review.md · skills/interrogate/references/
  • lead-judgment.md · skills/interrogate/references/
  • reviewer-prompt.md · skills/interrogate/references/
  • rubric.md · skills/interrogate/references/
  • SKILL.md · skills/loop/
  • loop-protocol.md · skills/loop/references/
  • SKILL.md · skills/maintain-verification-skill/
  • SKILL.md · skills/no-comments/
  • SKILL.md · skills/poteto-mode/
  • authoring-a-skill.md · skills/poteto-mode/playbooks/
  • autonomous-run.md · skills/poteto-mode/playbooks/
  • autopilot-full.md · skills/poteto-mode/playbooks/
  • autopilot-stack.md · skills/poteto-mode/playbooks/
  • babysit.md · skills/poteto-mode/playbooks/
  • bug-fix.md · skills/poteto-mode/playbooks/
  • eval.md · skills/poteto-mode/playbooks/
  • feature.md · skills/poteto-mode/playbooks/
  • hillclimb.md · skills/poteto-mode/playbooks/
  • investigation.md · skills/poteto-mode/playbooks/
  • multi-phase-plan.md · skills/poteto-mode/playbooks/
  • opening-a-pr.md · skills/poteto-mode/playbooks/
  • orchestrate.md · skills/poteto-mode/playbooks/
  • pause-safely.md · skills/poteto-mode/playbooks/
  • perf-issue.md · skills/poteto-mode/playbooks/
  • prototype.md · skills/poteto-mode/playbooks/
  • refactoring.md · skills/poteto-mode/playbooks/
  • runtime-forensics.md · skills/poteto-mode/playbooks/
  • session-pickup.md · skills/poteto-mode/playbooks/
  • shipping.md · skills/poteto-mode/playbooks/
  • trace-forensics.md · skills/poteto-mode/playbooks/
  • visual-parity.md · skills/poteto-mode/playbooks/
  • worktree-cleanup.md · skills/poteto-mode/playbooks/
  • …and 81 more

SKILL.md (first lines)

# Engineering rigor

A workflow skill set for agents doing real engineering work: match the task to a playbook, work
under explicit principles, delegate in isolated contexts, and prove the result against the real
artifact before claiming it works. It is a port of Lauren Tan's (poteto) pstack workflows, via
Joel Taroreh's agentic engineering framework.

Works on any agent that can run commands and spawn subagents. Nothing here names a product: skills
refer to **capabilities** (`shell`, `delegate`, `browser`, …) that you map onto whatever tools you
actually have. Read [`TOOLS.md`](TOOLS.md) first — it is the contract that makes the rest portable.

```
engineering-rigor/
├── SKILL.md            this file
├── TOOLS.md            capability vocabulary and how to map it to your tools
├── README.md           what this is, how to use it, provenance
├── rules/
│   ├── AGENTS.md       delegation, fan-out and verification invariants
│   └── models.md       per-role model classes
├── agents/             brief templates for the subagents you dispatch
├── scripts/            command gates (run them as CLIs)
├── skills/
│   ├── poteto-mode/    the engine: SKILL.md + 23 playbooks + references
│   ├── principle-*/    the 23 principle rules
│   └── <leaf skills>   how, why, recall, architect, arena, swarm, interrogate, deslop,
│                       no-comments, unslop, technical-writing, tdd, teach, reflect,
│                       blast-radius, figure-it-out, automate-me, loop, show-me-your-work,
│                       create-verification-skill, maintain-verification-skill,
│                       typescript-best-practices, bro
└── tests/              the skill set's own suite (catalog, hooks, invariants)
```

Paths in this skill set are relative to this directory unless stated otherwise.

## The contract

1. **Read [`TOOLS.md`](TOOLS.md), then [`skills/poteto-mode/SKILL.md`](skills/poteto-mode/SKILL.md)
   in full** — including its inline Principles index. That file is the engine; this one is the entry.
   Its **Non-negotiables** list is the trigger table.
2. **Open a todo list**, first item `read the Principles section`. Match the task to one of the 23
   playbooks in `skills/poteto-mode/playbooks/` and copy the matched playbook's steps in verbatim.
   A step you choose not to run stays in the list as `skip: <reason>`.
3. **Apply the principle you cite.** Name the principles that shaped a decision and the specific
   choice each one changed. A citation with no decision behind it means you skipped the leaf skill —
   read `skills/<principle-name>/SKILL.md` before claiming it.
4. **This is a mode, not a one-shot.** Once entered it stays on for the task across turns, applying
   itself when a playbook matches and staying out of the way otherwise. The user opts out by saying so.
5. **Write the reply per `unslop`** (`skills/unslop/SKILL.md`) and, for anything the user must act
   on, as a deliverable file under `artifacts/<task-slug>/` that you link in the reply.

## Non-negotiables

- **Delegation invariant.** Non-trivial code edits (>50 lines on one file, or multi-file) go to a
  subagent via `delegate`, which owns the diff in an isolated context. The coordinator plans, reads
  the diff, runs verification, and talks to the user — it does not write the bulk edit itself.
  Trivial edits (≤50 lines, new files, flags, ignore files, markdown, scratch scripts) are the
  coordinator's. Children usually cannot nest, so a child owns its diff directly. Gate it with
  `scripts/gate-delegation.sh <path> [content-file]`.
- **Dispatch, then end the turn.** If your `delegate` returns immediately, end the turn and let
  results arrive; never poll in a loop to wait. `rules/AGENTS.md` has the full protocol, including
  the watchdog.
- **Fan out for real.** Review, bakeoffs, and sweeps require actual concurrent subagents on
  different model classes. Simulating reviewer personas in the parent context is forbidden — it is
  the exact failure mode this skill set exists to prevent.
- **Prove it works.** Verify against the real artifact — run the feature, read the actual value,
  inspect the rendered page, read the diff — not against a proxy, a self-report, or "it compiles."
  See `skills/principle-prove-it-works/SKILL.md`.
- **Gate destructive commands** with `scripts/gate-safety.sh "<command>"` before running them
  unattended — it catches recursive root deletion, force-push to trunk, and `drop database`.
- **Long or unattended work leaves a trail.** `skills/show-me-your-work/SKILL.md` writes
  `decisions.tsv` + `decision_trail.md` under `artifacts/<task-slug>/`, incrementally, so a later
  turn can resume from disk rather than from conversation memory. Use `schedule` for heartbeats.

## Verify the install

```bash
ls skills/poteto-mode/playbooks | wc -l     # 23
sh scripts/gate-safety.sh "rm -rf /"        # a force_ask decision
python3 -m pytest tests/ -q                 # the skill set's own suite
```

If a skill's steps reference a capability you do not have, say so and use the closest substitute —
do not invent tool names, and do not silently skip the step. If a skill's steps reference a path
that no longer exists, fix that skill in place rather than working around it silently.

From harryhecanada/agent-skills, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 9, 2026 (19 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from harryhecanada

Cite this page

engineering-rigor skill. Agent Mart. https://agentmart.dev/skills/harryhecanada-engineering-rigor (last updated 2026-10-24)