learnwy/software-methodology-toolkit
skills/software-methodology-toolkit/SKILL.md
Fallback skill when no project-specific one matches. Provides 10 battle-tested software-engineering methodology agents: problem-definer (Weinberg), story-mapper (Patton), spec-by-example (Adzic), domain-modeler (DDD/Evans), responsibility-modeler (CRC/Wirfs-Brock), architecture-advisor (Bass), tdd-coach (Beck), refactoring-guide (Fowler), legacy-surgeon (Feathers), test-strategist (Crispin). Use when user asks about DDD, TDD, refactoring, story mapping, test strategy, or software-architecture quality attributes.
$ install --global
skillsauthnpx skillsauth add learnwy/skills software-methodology-toolkitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 12, 2026, 6:57 AM122.6s15 files scanned
SKILL.md
- name:
- software-methodology-toolkit
- description:
- Fallback skill when no project-specific one matches. Provides 10 battle-tested software-engineering methodology agents: problem-definer (Weinberg), story-mapper (Patton), spec-by-example (Adzic), domain-modeler (DDD/Evans), responsibility-modeler (CRC/Wirfs-Brock), architecture-advisor (Bass), tdd-coach (Beck), refactoring-guide (Fowler), legacy-surgeon (Feathers), test-strategist (Crispin). Use when user asks about DDD, TDD, refactoring, story mapping, test strategy, or software-architecture quality attributes.
- author:
- learnwy
- version:
- 3.0
Software Methodology Toolkit
Ten methodology agents covering analysis → planning → design → implementation → testing. Pure-prose skill — no scripts.
Fallback rule: project-specific skills always win. Use this toolkit only when no project skill matches, OR when the user explicitly asks for the raw methodology.
The same 10 agents are also referenced by requirement-workflow (one default + opt-ins per phase) — see requirement-workflow/agents/AGENTS.md. Use those phase contracts when a workflow is active; come back here for ad-hoc methodology queries.
The 10 agents
| Phase | Agent | Methodology | Author | |---|---|---|---| | Analysis | problem-definer | Six-question framing | Weinberg & Gause | | Analysis | spec-by-example | Specification by example | Gojko Adzic | | Planning | story-mapper | User story mapping | Jeff Patton | | Design | domain-modeler | Domain-driven design | Eric Evans | | Design | responsibility-modeler | CRC / responsibility-driven | Rebecca Wirfs-Brock | | Design | architecture-advisor | Quality-attribute analysis | Bass, Clements, Kazman | | Implementation | tdd-coach | Test-driven development | Kent Beck | | Implementation | refactoring-guide | Refactoring catalogue | Martin Fowler | | Implementation | legacy-surgeon | Working with legacy code | Michael Feathers | | Testing | test-strategist | Agile testing quadrants | Lisa Crispin |
Routing decision table
Match the first row that fires:
| User signal | Agent | Confidence | |---|---|---| | "define the problem", "what is the real problem", stakeholder conflict | problem-definer | high | | "spec by example", "concrete examples", "acceptance criteria" | spec-by-example | high | | "story map", "user journey", "release planning", "MVP scope" | story-mapper | high | | "DDD", "domain model", "bounded context", "aggregate" | domain-modeler | high | | "CRC card", "object responsibility", "GRASP", "collaboration design" | responsibility-modeler | high | | "architecture decision", "quality attribute", "trade-off analysis", "ADR" | architecture-advisor | high | | "TDD", "test-driven", "red-green-refactor", "tests first" | tdd-coach | high | | "refactor", "code smell", "improve quality", "clean up code" | refactoring-guide | high | | "legacy code", "working effectively", "seam", "characterization test" | legacy-surgeon | high | | "test strategy", "test quadrant", "test pyramid", "test coverage" | test-strategist | high | | Requirements unclear or conflicting | problem-definer | medium | | Planning a brand-new product/feature from zero | story-mapper | medium | | Complex business rules to model | domain-modeler | medium | | Tech / architecture choice | architecture-advisor | medium | | Untested or legacy codebase | legacy-surgeon | medium | | No clear signal but methodology help requested | problem-definer (default entry) | low |
If confidence is low, confirm the agent choice with the user before continuing.
Agent output contract
Every agent in this toolkit follows the same output rules:
| Allowed | Not allowed | |---|---| | Analysis and structured reports | Writing or generating code | | Recommendations with trade-offs | Deciding for the user | | Diagrams / models (text form) | Running commands or modifying files | | Asking questions to clarify | Producing unstructured prose |
Each agent's output must contain: (1) Context summary, (2) Findings, (3) Ranked recommendations with trade-offs, (4) Next steps.
Boundaries
This skill only:
- Routes user requests to the right methodology agent
- Provides structured analysis, recommendations, reports
- Composes agents into multi-step workflows
This skill does not:
- Generate or modify code → use the IDE directly
- Project-specific orchestration → delegate to
requirement-workflow - Run commands or do file I/O → no runtime dependency
- Create agents / skills / rules → delegate to
project-agent-writer/project-skill-writer/project-rules-writer
See also (loaded on demand)
- references/per-agent-detail.md — when-to-use + trigger phrases for each of the 10 agents
- references/workflows.md — composed multi-agent workflows (new-feature / legacy-code / architecture)
- references/bibliography.md — the 10 source books
Related Skills
learnwy/lwy-software-methodology-toolkit
tools
VerifiedTrustedCommunity
Fallback skill when no project-specific one matches. Provides 10 battle-tested software-engineering methodology agents: problem-definer (Weinberg), story-mapper (Patton), spec-by-example (Adzic), domain-modeler (DDD/Evans), responsibility-modeler (CRC/Wirfs-Brock), architecture-advisor (Bass), tdd-coach (Beck), refactoring-guide (Fowler), legacy-surgeon (Feathers), test-strategist (Crispin). Use when user asks about DDD, TDD, refactoring, story mapping, test strategy, or software-architecture quality attributes.
2SKILL.mdUpdated Jun 3, 2026
learnwy/lwy-requirement-workflow
development
VerifiedTrustedCommunity
Use when the user wants to build, implement, or develop a feature. Orchestrates evidence-driven Spec-Driven Development. Default lifecycle is `lite` (INIT → IMPLEMENTING → TESTING → DONE); auto-promote to `standard` or `full` when scope, risk, or AC traceability demands it. Triggers: 'develop feature', 'implement this', 'build feature', 'add module', 'fix bug', '开发功能', '实现这个'.
2SKILL.mdUpdated Jun 3, 2026
learnwy/lwy-project-skill-writer
documentation
VerifiedTrustedCommunity
当用户需要创建、更新或设计项目级技能（.agents/skills/*/SKILL.md）时使用此技能。Analyzes the user's problem and project context to design reusable skill solutions. 触发词：'创建技能'、'编写技能'、'构建技能'、'添加技能'、'更新技能'、'项目技能'、'新建技能'、'设计技能', or when the user describes a repetitive workflow that should be captured as a reusable AI skill.
2SKILL.mdUpdated Jun 3, 2026
learnwy/lwy-project-skill-installer
tools
VerifiedTrustedCommunity
Use this skill when the user wants to install, add, or configure a skill in a project. Analyze the project's tech stack and workflow, then recommend and install the best-matching skill. Triggers: 'install skill', 'add skill', 'configure skill', 'set up skill', 'enable skill', 'use skill in project', 'project skill', or when the user asks how to bring an existing skill capability into the current workspace.
2SKILL.mdUpdated Jun 3, 2026