agentleFS
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/dev-methodology/SKILL.md

methodology

Skill4 starsChanged 28 days agoMITView on GitHub

[UDS] Select and track the active development methodology (SDD, BDD, TDD) for a project. Use when: deciding which methodology a project should follow, switching methodology, checking which phase the current methodology is in. Not for: finding which command to run at a given development stage — use /dev-workflow; executing a methodology itself — use /sdd, /bdd, or /tdd. Keywords: methodology, SDD, BDD, TDD, phase tracking, methodology selection, 方法論, 開發方法選擇, 階段追蹤.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After /methodology completes, the AI assistant should suggest based on the selected methodology:

    line 94

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Methodology System | 方法論系統

[!WARNING] Experimental Feature / 實驗性功能

This feature is under active development and may change significantly in v4.0. 此功能正在積極開發中,可能在 v4.0 中有重大變更。

Select and manage the active development methodology for the current project. This skill focuses on choosing which methodology to use (SDD, BDD, TDD) and tracking phase progress within the chosen methodology.

選擇並管理當前專案的開發方法論。此技能專注於選擇使用哪種方法論(SDD、BDD、TDD)並追蹤所選方法論內的階段進度。

Related: For navigating development phases and finding the right UDS command at each stage, use /dev-workflow instead.

相關:如需查詢開發階段對應的 UDS 指令,請改用 /dev-workflow。

When to Use /methodology vs /dev-workflow | 何時使用

Scenario/methodology/dev-workflow
Choose SDD vs BDD vs TDD✅❌
Switch between methodologies✅❌
Track current phase progress✅❌
Find the right UDS command for a task❌✅
Get step-by-step workflow for new feature / bug fix❌✅
Navigate 8 development phases❌✅

Two Independent Systems / 兩個獨立系統:

  • System A: SDD - Spec-Driven Development (AI-era, spec-first)
  • System B: Double-Loop TDD - BDD (outer) + TDD (inner) (traditional)

Optional Input: ATDD - Acceptance Test-Driven Development (feeds into either system)

Actions | 動作

ActionDescription說明
(none) / statusShow current phase and checklist顯示當前階段和檢查清單
switch <id>Switch to different methodology切換到不同方法論
phase [name]Show or change current phase顯示或變更當前階段
checklistShow current phase checklist顯示當前階段檢查清單
skipSkip current phase (with warning)跳過當前階段(會有警告)
listList available methodologies列出可用方法論
createCreate custom methodology建立自訂方法論

Available Methodologies | 可用方法論

SystemIDWorkflow工作流程
A: SDDsdd/sdd -> Review -> /derive-all -> Implementation規格優先
B: BDDbddDiscovery -> Formulation -> Automation外部迴圈
B: TDDtddRed -> Green -> Refactor內部迴圈
InputatddWorkshop -> Examples -> Tests驗收測試驅動

Usage Examples | 使用範例

/methodology                    # Show current status
/methodology switch sdd         # Switch to Spec-Driven Development
/methodology phase green        # Move to GREEN phase (TDD)
/methodology checklist          # Show current phase checklist
/methodology list               # List all available methodologies
/methodology skip               # Skip current phase (with warning)
/methodology create             # Start custom methodology wizard

Configuration | 配置

Methodology settings are stored in .standards/manifest.json:

{
  "methodology": {
    "active": "sdd",
    "available": ["tdd", "bdd", "sdd", "atdd"]
  }
}

Next Steps Guidance | 下一步引導

After /methodology completes, the AI assistant should suggest based on the selected methodology:

方法論已設定。建議下一步 / Methodology configured. Suggested next steps:

  • SDD 方法論 → 執行 /sdd 建立規格 ⭐ Recommended / 推薦 — SDD → Run /sdd to create spec
  • BDD 方法論 → 執行 /bdd 開始場景探索 — BDD → Run /bdd to start discovery
  • TDD 方法論 → 執行 /tdd 開始紅綠重構 — TDD → Run /tdd to start Red-Green-Refactor
  • ATDD 方法論 → 執行 /atdd 定義驗收條件 — ATDD → Run /atdd to define AC

Reference | 參考

  • Create Custom Methodology Guide — Read it when building a custom methodology rather than using a shipped one.
  • Integrated Development Flow Guide — Read it when combining several methodologies into one flow.
  • Workflow Prerequisite Checking / 工作流前置步驟檢查 — Read it when a workflow step needs its prerequisites checked first.
  • Methodology Runtime Guide — Read it when you need to know how a methodology behaves while it runs.
  • Detailed guide: guide.md

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件:/methodology

For complete AI agent behavior definition, see the corresponding command file: /methodology

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.