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
- xiaoyangtx996/Searching-skilltheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- AsiaOstrich/universal-dev-standardsword for word, first seen Nov 4, 2026
- pavel-molyanov/molyanov-ai-devtheir own version, first seen Oct 25, 2026
- AlexHorovitz/skillstheir own version, first seen Oct 17, 2026
- stepanenkoviktor0110-boop/ai-dev-methodologytheir own version, first seen May 31, 2026
Other versions7 projects use a version of this.
Word for word · 1
- AsiaOstrich/universal-dev-standards★ 84100% same
Edited · 0
None found.
Wrote their own version · 6
- pavel-molyanov/molyanov-ai-dev★ 299same name
- 0x-Shashi/WEB3-AUDIT-SKILLS★ 61same name
- paureis/pau-skills★ 2same name
- stepanenkoviktor0110-boop/ai-dev-methodology★ 2same name
- AlexHorovitz/skills★ 1same name
- xiaoyangtx996/Searching-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- commitSkill
- contract-testSkill
- databaseSkill
- deploySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- spec-deriveSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill
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
- Very specific: line 94
After /methodology completes, the AI assistant should suggest based on the selected methodology:
“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.
Files
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-workflowinstead.相關:如需查詢開發階段對應的 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 | 動作
| Action | Description | 說明 |
(none) / status | Show current phase and checklist | 顯示當前階段和檢查清單 |
switch <id> | Switch to different methodology | 切換到不同方法論 |
phase [name] | Show or change current phase | 顯示或變更當前階段 |
checklist | Show current phase checklist | 顯示當前階段檢查清單 |
skip | Skip current phase (with warning) | 跳過當前階段(會有警告) |
list | List available methodologies | 列出可用方法論 |
create | Create custom methodology | 建立自訂方法論 |
Available Methodologies | 可用方法論
| System | ID | Workflow | 工作流程 |
| A: SDD | sdd | /sdd -> Review -> /derive-all -> Implementation | 規格優先 |
| B: BDD | bdd | Discovery -> Formulation -> Automation | 外部迴圈 |
| B: TDD | tdd | Red -> Green -> Refactor | 內部迴圈 |
| Input | atdd | Workshop -> 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 wizardConfiguration | 配置
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/sddto create spec- BDD 方法論 → 執行
/bdd開始場景探索 — BDD → Run/bddto start discovery- TDD 方法論 → 執行
/tdd開始紅綠重構 — TDD → Run/tddto start Red-Green-Refactor- ATDD 方法論 → 執行
/atdd定義驗收條件 — ATDD → Run/atddto 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 行為定義請參閱對應的命令文件:
/methodologyFor complete AI agent behavior definition, see the corresponding command file:
/methodology
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
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.

