// detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment
| name | development-workflow |
| description | detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment |
| Triggers | deployment, development, hub-and-spoke, modular, code |
| created_by | abstract-examples |
| tags | ["development","workflow","modular","hub-and-spoke"] |
| category | workflow |
| type | hub |
| estimated_tokens | 45 |
| dependencies | [] |
| companion_skills | [] |
| modules | ["git-workflow","code-review","testing-strategies","documentation-guidelines","deployment-procedures"] |
| tools | ["setup-validator","workflow-checker","quality-metrics"] |
This modular skill provides a detailed framework for software development workflows. It's designed as a hub that coordinates specialized modules for different aspects of development.
Get started quickly with this development workflow framework:
** Quick Start**: Set up repository structure and basic workflow in minutes
Progressive Learning: Start simple, add complexity as needed
** Use Case-Based**: Jump directly to what you need
This workflow includes these specialized modules:
To use this development workflow:
Set up your development environment:
Use git-workflow module for repository initialization and branching setup
Verification: Run the command with --help flag to verify availability.
Follow the development cycle:
**Verification:** Run the command with `--help` flag to verify availability.
git-workflow → code-review → testing-strategies → documentation-guidelines
Verification: Run pytest -v to verify tests pass.
Deploy and monitor:
**Verification:** Run the command with `--help` flag to verify availability.
deployment-procedures module handles CI/CD and production monitoring
Verification: Run the command with --help flag to verify availability.
Start with git-workflow to establish repository structure, then progress through modules as your project develops.
Use individual modules to improve specific areas:
Guide new team members through the modules in order to establish consistent practices.
This modular approach provides several advantages over monolithic workflows:
Each module includes validation tools to validate best practices:
Use the quality-metrics tool to assess your workflow implementation:
quality-metrics --workflow development-workflow --modules all
Verification: Run the command with --help flag to verify availability.
This workflow is designed to be adaptable:
See the modules directory for detailed documentation on:
Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag
Create Azure cloud architecture diagrams in SVG format using official Microsoft Azure icons. Use when the user asks to create, generate, or draw an Azure architecture diagram, cloud diagram, infrastructure diagram, or any visual showing Azure services. Also trigger when user mentions creating diagrams for Azure Fabric, AKS, App Service, Functions, or any Azure service topology.
NEVER escalate without investigation first. This is the Iron Law. Use when evaluating whether to escalate models, facing genuine complexity requiring deeper reasoning, novel patterns with no existing solutions, high-stakes decisions requiring capability investment. Do not use when thrashing without investigation - investigate root cause first. DO NOT use when: time pressure alone - urgency doesn't change task complexity. DO NOT use when: "just to be safe" - assess actual complexity instead.
Use this skill BEFORE writing any hook. Check even if unsure. Use when creating new hooks for tool validation, logging operations for audit, injecting context before prompts, enforcing project-specific workflows, preventing dangerous operations in production. Do not use when logic belongs in core skill - use Skills instead. DO NOT use when: complex multi-step workflows needed - use Agents instead. DO NOT use when: behavior better suited for custom tool.
Use this skill BEFORE deploying hooks to production. Use when auditing existing hooks for security vulnerabilities, benchmarking hook performance, implementing hooks using Python SDK, understanding hook callback signatures, validating hooks against compliance standards. Do not use when deciding hook placement - use hook-scope-guide instead. DO NOT use when: writing hook rules from scratch - use hook-authoring instead. DO NOT use when: validating plugin structure - use validate-plugin instead.
Surfaces expert frameworks and proven methodologies before creating OR evaluating skills, hooks, agents, or commands. Helps select approaches from domain masters. Use when starting creation workflows, evaluating methodology gaps, or seeking domain expertise. Do not use if you already have a specific methodology or are fixing syntax/structural issues.
Architect skills as modular blocks to control token usage and complexity. Use when creating skills >150 lines, breaking down monolithic skills, or planning new architecture. Do not use for evaluating existing skills (use skills-eval) or writing human-facing prose (use writing-clearly-and-concisely). Check this skill before starting any new skill development.