dev-methodology Plugin
Documentation-driven development methodology for any codebase. Enforces a structured cycle: context loading, development, testing, documentation, and PR validation.
Installation
/plugin install dev-methodology@abilityai
Skills
| Skill | Description |
|---|---|
| /dev-methodology:init | Scaffold the methodology into your project |
| /dev-methodology:read-docs | Load project context at session start |
| /dev-methodology:implement | End-to-end feature implementation |
| /dev-methodology:validate-pr | Validate a PR against the methodology |
| /dev-methodology:commit | Create well-formatted commits |
| /dev-methodology:add-testing | Add tests to existing code |
| /dev-methodology:tidy | Clean up code |
| /dev-methodology:refactor-audit | Review changed code for reuse, quality, and efficiency |
| /dev-methodology:roadmap | Query issues for roadmap priorities |
| /dev-methodology:security-check | Quick security scan |
| /dev-methodology:security-analysis | Deep OWASP-based security analysis |
| /dev-methodology:feature-flow-analysis | Create or update a feature flow document |
| /dev-methodology:sync-feature-flows | Analyze code changes and update affected feature flows |
| /dev-methodology:update-docs | Update project documentation after making changes |
| /dev-methodology:generate-user-docs | Generate user-facing docs from source code |
How It Works
Initialize Methodology
/dev-methodology:init
Scaffolds into your project: docs/memory/ (architecture and requirements docs), docs/memory/feature-flows/ (vertical slice documentation), and .claude/skills/ (development playbooks).
Session Start
/dev-methodology:read-docs
Loads project context: architecture overview, current requirements, recent changes, and active feature flows.
Feature Implementation
/dev-methodology:implement #42
End-to-end flow: read the issue and understand requirements, plan the implementation, write code with tests, update documentation, and create a PR.
PR Validation
/dev-methodology:validate-pr 123
Checks: code quality and style, test coverage, documentation updates, security considerations, breaking changes.
Development Cycle
The methodology enforces a 5-phase cycle:
1. Context 2. Plan 3. Implement 4. Document 5. Validate
read-docs understand write code update-docs validate-pr
requirements write tests feature flowsSecurity Tools
Quick Scan
/dev-methodology:security-check
Fast checks for common issues: hardcoded secrets, SQL injection patterns, XSS vulnerabilities.
Deep Analysis
/dev-methodology:security-analysis
Comprehensive OWASP-based review: authentication flows, authorization checks, input validation, data exposure.