Dev workflow

Skill myenquiringmind/dev-standards-plugin/skills/dev-workflow

Enforces best practice development workflow for any code task. Triggers on: feature implementation, bug fixes, refactoring, code changes, debugging, testing, and any development work. Ensures DRY/SOLID principles, comprehensive testing, validation, proper git commits, and structured planning with TLDR summaries.From its SKILL.md

Install

npx -y skills add myenquiringmind/dev-standards-plugin --skill dev-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, as published. Nobody here has run it

Development Workflow

Core Principle

Investigate → Plan → Implement → Test → Validate → Commit

Never skip steps. The most common failures come from implementing without understanding.

Quick Reference

Task	Command	Subagent
Create plan	`/plan`	-
Fix a bug	`/fix`	`@operate-root-cause-analyst`
Validate changes	`/validate`	-
Code review	`/review`	`@validation-code-reviewer`
Write tests	-	`@test-writer`
Update docs	-	`@doc-technical-writer`

Workflow by Task Type

Bug Fix

Delegate to @operate-root-cause-analyst for root cause analysis
/plan the fix with TLDR
Implement on feature branch
/validate all changes
Commit with fix(scope): description

New Feature

/plan with requirements breakdown
Implement incrementally
Delegate @test-writer for coverage
/review before completion
/validate and commit

Refactoring

Ensure tests exist first (delegate @test-writer if not)
/plan the refactoring approach
Make small, incremental changes
Run tests after each change
/validate behavior unchanged

Code Quality Standards

DRY (Don't Repeat Yourself)

Extract to function when pattern appears 3+ times
Create shared utilities for cross-module patterns
Use constants for magic numbers/strings

SOLID Principles

Single Responsibility: One function = one purpose
Open/Closed: Extend behavior without modifying existing code
Liskov Substitution: Subtypes must be substitutable
Interface Segregation: Small, focused interfaces
Dependency Inversion: Depend on abstractions

Error Handling

- Handle ALL error cases explicitly
- Fail fast with clear error messages
- Log errors with context for debugging
- Don't swallow exceptions silently

Git Commit Format

type(scope): brief description

- Detail about what changed
- Why it was changed
- Any breaking changes

Types: feat, fix, refactor, docs, test, chore, perf

Context Management

When to /compact

After completing a major milestone
Before starting unrelated work
When context exceeds ~50% (feeling sluggish)
After 15+ tool calls in a session

When to Delegate to Subagents

Independent analysis tasks
Parallel work opportunities
Specialized reviews (security, docs)
Tasks that would clutter main context

Response Format

TLDR (Always Include for Plans)

## TLDR
- **Problem**: [one sentence]
- **Solution**: [one sentence]
- **Steps**: [3-7 items]
- **Validation**: [how we verify]

Completion Report

## Complete

### Summary
[What was done]

### Validation
- Tests: ✅/❌
- Lint: ✅/❌
- Environment: ✅/❌

### Commit
[hash and message]

Anti-Patterns (Never Do These)

❌ Implement without investigating first ❌ Fix symptoms instead of root causes ❌ Skip validation ("it should work") ❌ Mark complete before tests pass ❌ Leave TODO placeholders in plans ❌ Make assumptions without verification ❌ Edit directly on main/master branch