engineering-flow

engineering-flow is a skill for Claude Code, Codex from danicat/skills. It costs 76 tokens per session (1,203 once invoked), scanned A, original, Apache-2.0.

A set of software engineering guidelines for planning, designing, and reviewing code changes. It covers RFCs, which are proposals for discussion, and ADRs, which record final architecture decisions.

In plain words
What is it for?
Use it to structure technical proposals, record architecture choices, prioritize tasks, apply versioning rules, and maintain cleaner code.
Why use it?
It helps teams turn uncertain ideas into documented decisions and keep implementation work small, testable, and focused. It also calls out problems such as unclear errors, dead code, and unnecessary abstractions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to structure technical proposals, record architecture choices, prioritize tasks, apply versioning rules, and maintain cleaner code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/danicat/skills/engineering-flow
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.

Any agent
npx skills add danicat/skills --skill engineering-flow
Clone the repo
git clone --depth 1 https://github.com/danicat/skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for engineering-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/danicat/skills/engineering-flow/github.svg)](https://agentmods.dev/skills/danicat/skills/engineering-flow)
Your own site
<a href="https://agentmods.dev/skills/danicat/skills/engineering-flow"><img src="https://agentmods.dev/badge/skills/danicat/skills/engineering-flow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for engineering-flow

Your own site · 80×15
<a href="https://agentmods.dev/skills/danicat/skills/engineering-flow"><img src="https://agentmods.dev/badge/skills/danicat/skills/engineering-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,203 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.01203
Opus 5.5 $0.00030 $0.00481
Sonnet 5.5 $0.00015 $0.00241
Haiku 4.5 $0.00008 $0.00120

Measured 1mo ago against content hash efb5186721d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

engineering-flow 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 1mo 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.

coding/engineering-flow/SKILL.md · 125 lines

How it starts

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

Engineering Flow

Engineering standards, decision pipelines, and code hygiene rules.


Delivery Principles

Ship working software in small, verifiable increments:

  • Keep changes scoped to a single logical objective.
  • Avoid speculative abstractions and overengineering.
  • Implement thin, vertical slices from entrypoint to persistence.
  • Verify each slice with automated tests and compiler checks before proceeding.

Design Pipeline: RFCs and ADRs

Separate exploration from permanent architectural choices:

graph TD
    A[Ambiguous Goal / High Uncertainty] --> B[RFC in design/rfc/]
    B -->|Consensus Reached| C[ADR in design/adr/]
    C --> D[Implementation Tasks]
    E[Trivial / Low-Uncertainty Task] --> D
  • RFCs (design/rfc/): Use during exploration when requirements are ambiguous, trade-offs need debate, or multiple viable architectures exist. RFCs are fluid working documents.
  • ADRs (design/adr/): Use to record finalized decisions. ADRs are immutable historical logs capturing context, chosen architecture, and accepted trade-offs.
  • Tasks: Break ADR conclusions into concrete checklist items with clear acceptance criteria.

Task Prioritization

Categorize work by technical certainty and business value:

High Technical Certainty Low Technical Certainty
High Value Direct execution: Implement interactively with compiler feedback and tight test loops. Research & Spikes: Do not write production code yet. Run throwaway spikes in scratch/ or draft an RFC.
Low Value Delegate: Offload to background tasks or subagents. Defer / Discard: Drop or postpone until certainty increases or value is demonstrated.

Research & Evidence Hierarchy

Do not guess APIs, package syntax, or model behaviors. Ground technical decisions in primary sources:

[1] Source Code (highest authority)
  └── [2] Official Documentation & API Reference
        └── [3] Official Release Notes & Announcements
              └── [4] Industry Expert Articles (< 3 months old)
                    └── [5] Community Posts (< 3 months old)
                          └── [6] Stale Articles (> 3 months old — discard)
                                └── [7] Social Media (unverified — cross-check first)

Read the full file on GitHub · 125 lines

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.

  1. 1mo ago First seen · 125 lines · 76 tokens per session scan A efb5186721d6

Subscribe to this mod's changes

engineering-flow is a skill published in the GitHub repository danicat/skills (20 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,203 once invoked, about $0.0003 per session on Opus 5.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-30.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens