workflow
/workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
- Author
- claude-world ↗
- Repository
- director-mode-lite ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
Original author description
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
How it works
- Overview
- Step 1: Focus Problem (/focus-problem)
- Step 2: Prevent Overdev
- Step 3: Test First (/test-first)
- Step 4: Document
- Step 5: Smart Commit (/smart-commit)
- Quick Start
- Related Skills
SKILL.md preview
--- name: workflow description: "Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow." user-invocable: true --- # Development Workflow A structured approach to software development that emphasizes understanding, minimal implementation, testing, documentation, and clean commits. --- ## Overview ``` Step 1: Focus Problem → Understand before coding Step 2: Prevent Overdev → Only build what's needed (YAGNI) Step 3: Test First → Red-Green-Refactor Step 4: Document → Keep it clear and current Step 5: Smart Commit → Conventional Commits ``` --- ## Step 1: Focus Problem (`/focus-problem`) **Goal:** Thoroughly understand the problem before writing code. ### Checklist - [ ] What is the user need? (Who / What / Why) - [ ] What defines success? (How to verify completion?) - [ ] What are the boundaries? (What NOT to do?) - [ ] What files/modules are affected? - [ ] Is there existing similar functionality? ### Use Explore Agent (Use the active provider's native dispatcher; Claude pseudo-code is shown below.) Before dispatch, preserve the bounded exploration request and expected result. If Claude's Agent tool is unavailable or withheld, or Codex's `spawn_agent` interface is unavailable or withheld, the maximum depth is reached, or a concurrency limit rejects the call, do not retry or substitute assumptions. Return an incomplete `dispatch_request` and do not advance the workflow. Choose exactly one provider-native form: - Claude Code: `Agent(subagent_type="Explore", model="haiku", prompt="<bounded prompt>")` - Codex CLI: `spawn_agent(agent_type="explorer", task_name="workflow_explore", message="<bounded prompt>")` ```markdown Agent(subagent_type="Explore", model="haiku", prompt=""" Explore the codebase for: [feature name] (thoroughness: medium) Find related files, similar implementations, and test patterns. """) ``` In Codex, send the same exploration request through `spawn_agent(...)`; do not invoke the Claude example as a second dispatch. --- ## Step 2: Prevent Overdev **Goal:** Ensure minimal viable implementation (YAGNI principle). ### Red Flags ``` "We might need this later..." → Don't build it now "Just in case..." → YAGNI "Let's make it generic..." → Solve current problem only "We should create a framework..." → Write concrete implementation ``` ### Checklist - [ ] Is there immediate need for this? - [ ] Is this over-abstracted? - [ ] Can this be simpler? - [ ] Are we adding unnecessary dependencies? --- ## Step 3: Test First (`/test-first`) **Goal:** Strict TDD (Red-Green-Refactor). ### Red Phase (Write Failing Test) - [ ] Write a test for expected behavior - [ ] Run test, confirm it fails - [ ] Failure message clearly indicates the issue ### Green Phase (Minimal Implementation) - [ ] Write minimum code to pass test - [ ] Don't optimize yet - [ ] Run test, confirm it passes ### Refactor Phase - [ ] Clean up code (keep tests passing) - [ ] Remove duplication - [ ] Improve naming - [ ] Simplify logic --- ## Step 4: Document **Goal:** Ensure code is understandable. ### Checklist - [ ] README describes purpose and usage - [ ] Public APIs have docstrings - [ ] Complex logic has comments explaining "why" - [ ] No obvious-comment clutter --- ## Step 5: Smart Commit (`/smart-commit`) **Goal:** Clean version history with Conventional Commits. ### Format ``` <type>(<scope>): <description> ``` ### Types - `feat` - New feature - `fix` - Bug fix - `docs` - Documentation - `test` - Tests - `refactor` - Code restructure --- ## Quick Start ```bash # Run full workflow /workflow # Or individual steps /focus-problem "implement user login" /test-first /smart-commit ``` --- ## Related Skills | Skill | Purpose | |-------|---------| | `/focus-problem` | Step 1: Problem analysis | | `/test-first` | Step 3: TDD cycle | | `/smart-commit` | Step 5: Create commit | | `/plan` | Break down complex tasks |
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · claude-world/director-mode-lite | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| SimHacker/moollm | 100 | MIT |
| mlophez/polix-ai | 100 | Apache-2.0 |
| stellarie/minimal-agent-kit | 100 | MIT |
| waynesutton/builder-skills | 100 | Apache-2.0 |
| DawitLemmaBalcha/agent-workflow | 100 | MIT |
| zhinkgit/embeddedskills | 100 | MIT |
| anthillapp/anthill | 100 | MIT |
Database snapshot: 13.11.2026 · package version 45f4972d7453 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100tdd
Test-driven development workflow. Use when the user asks to "write tests first", "TDD", "add test coverage", "test this function", or wants to develop a feature test-first. - 95development-workflow
Complete workflow from new Hook/Component/Util development to deployment. Use when starting new feature development. - 95tdd-workflow
Test-Driven Development workflow enforcement skill. Use when explicitly asked for TDD methodology, test-first development, red-green-refactor cycle, or TDD implementation. Triggers on keywords like "start TDD", "test-driven development", "write tests first", or in Chinese "開始… - 100tdd-workflow
TDD red-green-refactor workflow. Use when implementing a feature or bug fix test-first. - 95tdd-workflow
Test-driven development workflow for R using testthat. Use when writing new features, fixing bugs, or refactoring code. Enforces test-first development with 80%+ coverage. - 100test-driven-development
Explicit `/test-driven-development` reference for a strict test-first workflow. Use only when the user explicitly requests TDD, "test first", or "테스트 먼저"; do not auto-apply during routine implementation.