dev-understand

dev-understand is a skill for Claude Code, Codex from movebrickschi/harness-engineering-mcp. It costs 109 tokens per session (1,278 once invoked), scanned A, original, MIT.

A requirements-discovery workflow for examining a working prototype and turning its behaviour into plain business documents. It keeps the prototype read-only and uses back-and-forth questions to clarify unclear points.

In plain words
What is it for?
Use it to explore a product manager’s prototype, document how a feature should work, describe its API and data model, and resolve open questions before coding.
Why use it?
It prevents developers from copying implementation details or starting with vague requirements. The result gives later development a shared description of the business flow, interfaces, data, and environment.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for gstack. Also seen: mentions subagents; built for gstack.

Good fit Use it to explore a product manager’s prototype, document how a feature should work, describe its API and data model, and resolve open questions before coding.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/movebrickschi/harness-engineering-mcp/dev-understand
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 movebrickschi/harness-engineering-mcp --skill dev-understand
Clone the repo
git clone --depth 1 https://github.com/movebrickschi/harness-engineering-mcp

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 dev-understand

README.md
[![agentmods](https://agentmods.dev/badge/skills/movebrickschi/harness-engineering-mcp/dev-understand/github.svg)](https://agentmods.dev/skills/movebrickschi/harness-engineering-mcp/dev-understand)
Your own site
<a href="https://agentmods.dev/skills/movebrickschi/harness-engineering-mcp/dev-understand"><img src="https://agentmods.dev/badge/skills/movebrickschi/harness-engineering-mcp/dev-understand/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 dev-understand

Your own site · 80×15
<a href="https://agentmods.dev/skills/movebrickschi/harness-engineering-mcp/dev-understand"><img src="https://agentmods.dev/badge/skills/movebrickschi/harness-engineering-mcp/dev-understand.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,278 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.
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.00109 $0.01278
Opus 5.5 $0.00044 $0.00511
Sonnet 5.5 $0.00022 $0.00256
Haiku 4.5 $0.00011 $0.00128

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

Security

Grade A, and why

dev-understand 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.

assets/skills/dev-understand/SKILL.md · 121 lines

How it starts

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

Dev Understand - 理解需求阶段

适用场景

完整开发流程的前置阶段。当 PM 给了原型项目,需要:

  • 探索清楚业务流程
  • 抽象化输出需求文档
  • 通过 PM 沟通消除需求模糊点
  • 为后续开发阶段(/dev-implement)准备好需求知识库

核心原则

  1. A 项目只读:进入立即 /freeze + SwitchMode 到 plan 模式
  2. 抽象化输出:禁止把 A 的具体代码搬到文档里,要翻译成业务语言
  3. PM 沟通可循环:支持多轮往返,用 AskQuestion 阻塞等待

启动参数收集

使用 AskQuestion 工具一次性收集(用户消息已含则跳过):

  1. 需求名称(kebab-case,如 supplier-batch-approve)
  2. 原型项目 A 路径(智能推断后确认)
  3. 原型功能 URL
  4. PM 联系人

写入 ~/Projects/_requirements/[feature]/META.md。

流程执行

阶段 0:上下文初始化

  1. 创建 ~/Projects/_requirements/[feature]/ 目录
  2. 写入 META.md
  3. 加载 ~/Projects/_requirements/_lessons.md(如存在)作为背景
  4. 输出执行计划

阶段 1:A 项目探索(只读)

  1. move_agent_to_root 切到 A 项目
  2. 立即 /freeze + SwitchMode 到 plan
  3. 浏览器走查目标 URL:
    • browser_snapshot + browser_take_screenshot
    • 点击所有可交互元素
    • browser_network_requests 抓 API
    • browser_console_messages 查报错
  4. 并行派 3 个 explore subagent:
    • 项目骨架(技术栈/结构/运行环境)
    • 目标功能前端(路由/组件/状态/API 调用)
    • 目标功能后端(路由/Controller/Service/Schema)
  5. 抽象化输出 4 份文档到 ~/Projects/_requirements/[feature]/:
    • BUSINESS_FLOW.md(业务流程,含截图、mermaid,无代码)
    • API_CONTRACT.md(接口契约,业务语言)
    • DATA_MODEL.md(数据模型,通用 ER)
    • ENV_NOTES.md(A 的运行环境特征)

文档模板位置:~/.cursor/skills/dev-flow-full/templates/(统一维护,避免重复):

  • META.md - 需求元信息
  • BUSINESS_FLOW.md - 业务流程
  • API_CONTRACT.md - 接口契约
  • DATA_MODEL.md - 数据模型
  • _lessons.md - 经验沉淀(已存在则追加)

读取模板后填充实际内容输出到 ~/Projects/_requirements/[feature]/。

阶段 2:需求循环 ⏸ 卡点(可循环)

  1. 用 gstack-office-hours 视角挑战需求文档
  2. 输出 questions-for-pm.md:
    • 模糊业务规则
    • 缺失边界场景
    • 互相矛盾点
    • 每个问题附 AI 猜测 + 需 PM 确认的具体点
  3. 调用 AskQuestion 阻塞等待:
    prompt: "需求文档已生成,请查看 questions-for-pm.md。请选择:"
    options:
      - "已和 PM 沟通,提供答复(粘贴在下条消息)"
      - "需求清楚无疑问,结束理解阶段"
      - "需要重新探索 A 项目某些细节"
    
  4. 收到 PM 答复后:
    • 更新需求文档
    • 追加到 pm-answers.md
    • 再次 AskQuestion 询问"还有疑问吗?"
    • 循环至用户选择"无疑问"

完成标志

输出本阶段总结:

✅ 理解需求阶段完成
📁 知识库位置:~/Projects/_requirements/[feature]/
📄 产出文档:
  - META.md
  - BUSINESS_FLOW.md
  - API_CONTRACT.md
  - DATA_MODEL.md
  - ENV_NOTES.md
  - questions-for-pm.md
  - pm-answers.md(如有)

下一步建议:使用 /dev-implement 进入开发实现阶段

Read the full file on GitHub · 121 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 · 121 lines · 0 tokens per session scan A d4d609540980

Subscribe to this mod's changes

dev-understand is a skill published in the GitHub repository movebrickschi/harness-engineering-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 1,278 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens