Agent skill

Product Diagnosis

by Stanshy in Stanshy/AgentHub

Six-question diagnostic framework for G0 pre-check — validate product direction before development starts

MITAuto-check passed

Install Product Diagnosis

skills CLI
$ npx skills add Stanshy/AgentHub --skill product-diagnosis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Stanshy/AgentHub product-diagnosis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Stanshy/AgentHub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.knowledge/company/skill-templates/product-diagnosis .claude/skills/product-diagnosis && rm -rf skills-src

Use ~/.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/

Facts

Skill name
product-diagnosis
GitHub stars
202
Token cost
~690 tokens
SKILL.md length
181 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Six-question diagnostic framework for G0 pre-check — validate product direction before development starts

  • Works in 3 steps: .knowledge/architecture.md — 系統架構 → .knowledge/coding-standards.md — 編碼規範 → .knowledge/postmortem-log.md — 是否有相關踩坑紀錄
  • Tasks that involve Skill authoring
  • SKILL.md covers 使用方式, 參數, 適用時機 and 六問診斷框架, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Diagnosis is an agent skill from Stanshy/AgentHub. Six-question diagnostic framework for G0 pre-check — validate product direction before development starts

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: One person, one software company. Manage 47 AI agents from a single Electron app — with Harness Engineering (Skills + Hooks + FileWatchers) for disciplined, traceable AI workflows. The licence is MIT.

When your agent uses it

  • Tasks that involve Skill authoring

Example prompts

  • “/product-diagnosis”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. .knowledge/architecture.md — 系統架構
  2. .knowledge/coding-standards.md — 編碼規範
  3. .knowledge/postmortem-log.md — 是否有相關踩坑紀錄

What it can do on your machine

Read from SKILL.md and the folder at commit 5300820. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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

Product Diagnosis loads about 690 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 181 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~690

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

The full file from Stanshy/AgentHub at commit 5300820, republished under its MIT licence (© Stanshy). 181 words, ~690 tokens.

Download SKILL.mdSave it as .claude/skills/product-diagnosis/SKILL.md (or your agent's skills folder).
name
product-diagnosis
description
Six-question diagnostic framework for G0 pre-check — validate product direction before development starts
allowed-tools
Read, Glob, Grep

產品診斷(G0 前置檢查)

在開發啟動前,用六問框架診斷產品方向,確保 G0 提案品質。

使用方式

/product-diagnosis <project-name>

參數

  • $ARGUMENTS: 專案名稱或描述(可選,若不提供則詢問)

適用時機

  • Sprint 提案書撰寫前
  • 新功能規劃前
  • PM 提出需求但方向不明確時
  • 老闆要求進行可行性評估時

六問診斷框架

依序回答以下六個問題,每個問題必須有明確結論:

Q1: 問題存在嗎?(Problem Validation)

我們要解決的問題,用戶真的有感嗎?

檢查項說明
痛點來源這個問題從哪裡來的?(用戶回饋 / 數據異常 / 老闆直覺 / 競品觀察)
頻率這個問題多常發生?(每天 / 每週 / 偶爾)
嚴重度不解決會怎樣?(流失用戶 / 降低效率 / 無影響)
現有替代方案用戶現在怎麼解決?成本高嗎?

結論: [ ] 問題真實存在且值得解決 / [ ] 問題存在但優先級低 / [ ] 問題不成立


Q2: 目標用戶是誰?(User Definition)

這個功能是給誰用的?他們的使用場景是什麼?

檢查項說明
用戶角色老闆 / Agent / 兩者皆是
使用頻率每天 / 每週 / 每個 Sprint / 一次性
技術水平需要理解底層原理嗎?
關鍵場景描述 1-2 個最核心的使用場景

結論: [ ] 用戶輪廓清晰 / [ ] 需要進一步釐清


Q3: 解法合理嗎?(Solution Fitness)

我們提出的解法,是不是最簡單有效的?

檢查項說明
複雜度 vs 價值實作成本和帶來的價值成比例嗎?
有沒有更簡單的做法能用現有功能組合解決嗎?能用 Skill/Hook 而非新 IPC 嗎?
技術可行性在當前架構下可行嗎?需要大改架構嗎?
邊界情況有沒有明顯的 edge case 會讓方案崩潰?

結論: [ ] 解法合理 / [ ] 有更好的替代方案 / [ ] 技術上有風險


Q4: 範圍明確嗎?(Scope Clarity)

這個任務的邊界在哪裡?什麼做、什麼不做?

檢查項說明
必做(Must Have)列出核心功能點
不做(Out of Scope)明確排除哪些功能
驗收標準怎麼判斷「做完了」?
依賴需要其他任務先完成嗎?

結論: [ ] 範圍清晰可執行 / [ ] 範圍過大需拆分 / [ ] 範圍模糊需釐清


Q5: 符合架構嗎?(Architecture Alignment)

這個功能和現有架構一致嗎?會破壞什麼嗎?

讀取以下文件進行比對:

  1. .knowledge/architecture.md — 系統架構
  2. .knowledge/coding-standards.md — 編碼規範
  3. .knowledge/postmortem-log.md — 是否有相關踩坑紀錄
檢查項說明
IPC 四方同步新增 IPC 通道是否遵守四方同步規則?
資料流向資料從哪來到哪去?有沒有繞過正規路徑?
命名規範新增的命名是否符合現有慣例?
歷史教訓postmortem-log 中有沒有相關的踩坑紀錄?

結論: [ ] 符合架構 / [ ] 需要小幅調整 / [ ] 需要架構決策(提交老闆)


Q6: 風險可控嗎?(Risk Assessment)

最壞的情況是什麼?我們能承受嗎?

風險類型評估
時間風險能在 1 個 Sprint 內完成嗎?
技術風險有沒有不確定的技術難題?
回歸風險會不會破壞現有功能?
維護風險未來維護成本高嗎?

結論: [ ] 風險可控 / [ ] 中等風險需監控 / [ ] 高風險建議延後


診斷報告輸出格式

完成六問後,輸出以下摘要:

markdown
# 產品診斷報告

**專案**: {project-name}
**診斷日期**: {today}
**診斷人**: Tech Lead

## 診斷摘要

| # | 診斷問題 | 結論 | 備註 |
|---|---------|------|------|
| Q1 | 問題存在嗎? | {結論} | {一句話說明} |
| Q2 | 目標用戶是誰? | {結論} | {一句話說明} |
| Q3 | 解法合理嗎? | {結論} | {一句話說明} |
| Q4 | 範圍明確嗎? | {結論} | {一句話說明} |
| Q5 | 符合架構嗎? | {結論} | {一句話說明} |
| Q6 | 風險可控嗎? | {結論} | {一句話說明} |

## 總體建議

[ ] 建議通過 G0,可進入開發
[ ] 建議修改後再提交 G0(附修改建議)
[ ] 建議暫緩(附原因)
[ ] 建議取消(附原因)

## 修改建議(若有)

{具體的修改建議}

注意事項

  • 此 Skill 僅產出診斷報告,不做任何程式碼修改
  • 診斷結果呈報老闆,由老闆決定是否通過 G0
  • 若多個問題結論為負面,強烈建議暫緩開發
  • Q5 架構比對必須讀取實際文件,不可憑記憶回答

© Stanshy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .knowledge/company/skill-templates/product-diagnosis of Stanshy/AgentHub.

Open the folder on GitHubat commit 5300820

Compare with similar skills

Product Diagnosis 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.

Product Diagnosis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Diagnosis this skillStanshy/AgentHub202—~690Automated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Nuwa Thinking-Style Skill Builderalchaincyf/nuwa-skill34k—~4.6kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Claude Code Command Developmentanthropics/claude-plugins-official38k10 repos~4.8kAutomated safety check: PassApache-2.0

Similar skills

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Researches a person or theme and distills how they think into a runnable persona skill with mental models, decision rules and a characteristic voice.

    34k GitHub stars~4.6k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed
  • Book to Skill Converter

    virgiliojr94/book-to-skill

    Converts books and documents in PDF, EPUB, DOCX, HTML, Markdown, text, RTF or MOBI form into agent skills built from frameworks, principles, techniques and anti-patterns.

    34k GitHub stars~14k tokensUpdated 5 days ago
    Knowledge ManagementAuto-check passed

More from Stanshy/AgentHub

All 23 skills in this repo
  • Dev Plan

    Stanshy/AgentHub

    Generate a development plan with task breakdown and section 10 tracking tables

    202 GitHub stars~686 tokensUpdated 6 mo ago
    Auto-check: notes
  • Knowledge Feedback

    Stanshy/AgentHub

    Scan child projects for pitfalls and propose company standard updates

    202 GitHub stars~549 tokensUpdated 6 mo ago
    Auto-check: notes
  • Project Kickoff

    Stanshy/AgentHub

    Initialize new project with CLAUDE.md, .knowledge/ structure, company rules, and git

    202 GitHub stars~528 tokensUpdated 6 mo ago
    Auto-check: notes
  • Review

    Stanshy/AgentHub

    L1 internal review with auto-detection, design comparison, and Gate escalation path

    202 GitHub stars~854 tokensUpdated 6 mo ago
    Auto-check: notes
  • Sop Plan

    Stanshy/AgentHub

    L1 計畫模式 SOP — 強制上下文載入 + Plan Mode 評估 + 任務拆解. An agent skill from Stanshy/AgentHub.

    202 GitHub stars~437 tokensUpdated 6 mo ago
    Auto-check: notes
  • Sop Review

    Stanshy/AgentHub

    L1 Code Review SOP — 強制規範對照 + 審核決策,不得跳過任何 checkpoint. An agent skill from Stanshy/AgentHub.

    202 GitHub stars~522 tokensUpdated 6 mo ago
    Auto-check: notes

Questions about Product Diagnosis

What does Product Diagnosis do?

Six-question diagnostic framework for G0 pre-check — validate product direction before development starts. Product Diagnosis is an agent skill from Stanshy/AgentHub.

When should I use Product Diagnosis?

Product Diagnosis fits situations like: tasks that involve Skill authoring.

How do I install Product Diagnosis in Claude Code?

Run `npx skills add Stanshy/AgentHub --skill product-diagnosis -a claude-code`. Or copy the skill folder (.knowledge/company/skill-templates/product-diagnosis in Stanshy/AgentHub) into .claude/skills/product-diagnosis in your project. Claude Code loads it when a task matches its description.

How do I install Product Diagnosis in Codex?

Run `npx skills add Stanshy/AgentHub --skill product-diagnosis -a codex`. Or copy the skill folder (.knowledge/company/skill-templates/product-diagnosis in Stanshy/AgentHub) into .agents/skills/product-diagnosis in your project. Codex loads it when a task matches its description.

Can I use Product Diagnosis 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 Stanshy/AgentHub --skill product-diagnosis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-diagnosis, .gemini/skills/product-diagnosis, .github/skills/product-diagnosis and .opencode/skills/product-diagnosis in your project.

What does Product Diagnosis need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Diagnosis is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep.

Does Product Diagnosis 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 Product Diagnosis 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 Product Diagnosis use?

Product Diagnosis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Diagnosis use?

About 690 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Diagnosis?

Skills that share tags, products or a category with Product Diagnosis: Skill Creator (Azure/azqr, 796 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Nuwa Thinking-Style Skill Builder (alchaincyf/nuwa-skill, 34k stars) and Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Diagnosis?

Stanshy (a GitHub user) maintains it in Stanshy/AgentHub, which has 202 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on April 9, 2026.

Source: Stanshy/AgentHub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.