discipline-refactor-how-to-identify-disciplines
Sub-skill of discipline-refactor: How to Identify Disciplines.
Best use case
discipline-refactor-how-to-identify-disciplines is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of discipline-refactor: How to Identify Disciplines.
Teams using discipline-refactor-how-to-identify-disciplines should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/how-to-identify-disciplines/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How discipline-refactor-how-to-identify-disciplines Compares
| Feature / Agent | discipline-refactor-how-to-identify-disciplines | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of discipline-refactor: How to Identify Disciplines.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# How to Identify Disciplines ## How to Identify Disciplines 1. What are the main "nouns" in this repo? 2. What expertise areas does the code serve? 3. What would you call the team that owns each part? 4. Use consistent names across src/, tests/, docs/, specs/ ---
Related Skills
module-based-refactor
Reorganize a repository from flat structure to a module-based 5-layer architecture (src/tests/specs/docs/examples) while preserving git history. Use when restructuring a codebase into modules, migrating import paths, cleaning up hidden folders, consolidating duplicate directories, removing root-level artifacts, or archiving completed plan files. Capabilities: parallel agent spawn strategy, hidden-folder consolidation patterns, benchmark fixture separation, 4-phase atomic commit workflow.
discipline-refactor-verification-checklist
Sub-skill of discipline-refactor: Verification Checklist.
discipline-refactor-target-repository-structure
Sub-skill of discipline-refactor: Target Repository Structure.
discipline-refactor-standard-folders-module-structure
Sub-skill of discipline-refactor: Standard Folders → Module Structure (+1).
discipline-refactor-rollback
Sub-skill of discipline-refactor: Rollback.
discipline-refactor-phase-4-validation
Sub-skill of discipline-refactor: Phase 4: Validation.
discipline-refactor-phase-3-execution
Sub-skill of discipline-refactor: Phase 3: Execution.
discipline-refactor-phase-2-planning
Sub-skill of discipline-refactor: Phase 2: Planning.
discipline-refactor-phase-1-analysis
Sub-skill of discipline-refactor: Phase 1: Analysis.
discipline-refactor-orchestration-architecture
Sub-skill of discipline-refactor: Orchestration Architecture.
discipline-refactor-core-principles
Sub-skill of discipline-refactor: Core Principles.
discipline-refactor
Reorganize any repository by discipline/domain with module-based structure. Code in src/<pkg>/modules/, documents in <folder>/modules/. Orchestrates Explore, Plan, and general-purpose subagents. Works standalone.