ericgandrade/code-method
skills/code-method/SKILL.md
This skill should be used when the user wants an overview of the CODE Method (Context Oriented Development for Enterprises) — a structured SDLC framework with 9 specialized agents and 8 workflow phases covering discovery, planning, architecture, UX, stories, sprint management, implementation, and code review. Use when unsure which CODE Method skill to invoke, or when setting up the methodology on a new project.
$ install --global
skillsauthnpx skillsauth add ericgandrade/claude-superskills code-methodInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 3:50 AM245.7s1 file scanned
SKILL.md
- name:
- code-method
- description:
- This skill should be used when the user wants an overview of the CODE Method (Context Oriented Development for Enterprises) — a structured SDLC framework with 9 specialized agents and 8 workflow phases covering discovery, planning, architecture, UX, stories, sprint management, implementation, and code review. Use when unsure which CODE Method skill to invoke, or when setting up the methodology on a new project.
- license:
- MIT
Purpose
The CODE Method (Context Oriented Development for Enterprises) is a structured software development methodology that guides teams through the full SDLC using specialized AI agents and conversational workflows. It replaces ad-hoc prompting with repeatable, quality-gated phases — from product discovery to deployment.
When to Use
- Starting a new software project and unsure where to begin
- Onboarding a team to the CODE Method framework
- Exploring which agent or workflow to use for a specific task
- Setting up the methodology config for a project (
config.yaml) - Navigating between phases of an existing project
The 9 Agents
Each CODE Method skill embodies a specialized agent persona:
| Agent | Name | Role | Skill |
|-------|------|------|-------|
| Analyst | Mary | Discovery & market analysis | code-brief |
| Product Manager | James | PRD creation and validation | code-prd |
| Architect | William | Architecture decisions | code-architecture |
| UX Designer | Sophie | User experience planning | code-ux |
| Product Owner | Patricia | Epics & stories | code-stories |
| Scrum Master | Robert | Sprint planning & tracking | code-sprint |
| Developer | Tom | Story implementation | code-dev |
| QA Engineer | Carol | Adversarial code review | code-review |
| Orchestrator | Alex | Multi-agent coordination | code-method |
Workflow
Step 1: Identify Project State
Determine which SDLC phase the project is in:
Greenfield (new project):
→ code-brief → code-prd → code-ux → code-architecture
→ code-stories → code-sprint → [loop] code-dev → code-review
Brownfield (existing codebase):
Small change: → code-dev (quick mode)
Large change: → code-prd → code-architecture → code-stories → code-sprint → code-dev → code-review
Quick win / bug fix:
→ code-dev (quick-dev mode, no planning needed)
Step 2: Configure the Project
Create .code-method/config.yaml at the project root:
# CODE Method Configuration
user_name: "Your Name"
communication_language: "en-US"
output_folder: "docs"
artifacts_folder: ".code-output"
settings:
show_reasoning_chain: true
require_elicitation: true
auto_save_outputs: true
naming:
prd_prefix: "PRD-"
story_prefix: "STORY-"
epic_prefix: "EPIC-"
adr_prefix: "ADR-"
Step 3: Run the Appropriate Skill
Present the user with the full menu based on their project state:
Discovery Phase:
code-brief— Create a lightweight product brief before committing to a full PRDcode-prd— Create, validate, or edit a Product Requirements Document
Design Phase:
code-ux— Plan user experience, journeys, and design system decisionscode-architecture— Make architectural decisions (tech stack, patterns, structure)
Planning Phase:
code-stories— Decompose PRD + Architecture into epics and implementation-ready storiescode-sprint— Populate and track sprint status from epics
Implementation Phase:
code-dev— Implement a story (full mode) or execute a quick task (quick-dev mode)code-review— Run adversarial code review before merge
Step 4: Quality Gates
Enforce these gates before advancing phases:
| Gate | Requirement |
|------|------------|
| Before Architecture | PRD validated (>85% score, no critical gaps) |
| Before Stories | PRD + Architecture both complete |
| Before Sprint | Epics and stories created in epics.md |
| Before Merge | Code review completed, 0 critical issues, >80% test coverage |
Critical Rules
- NEVER skip the Product Brief + PRD phase for projects >1 day of development
- ALWAYS configure
config.yamlbefore starting a new project - NEVER merge code that has not passed
code-review - ALWAYS use
code-devquick mode for tasks <1 day; full mode for tasks >1 day - NEVER start architecture before the PRD exists and is validated
- ALWAYS save artifacts to the configured
artifacts_folder
Example Usage
User: "I need to build a new SaaS product"
→ Invoke code-method, then route to code-brief → code-prd
User: "Which CODE Method skill handles sprint tracking?"
→ Describe code-sprint, provide usage example
User: "Set up CODE Method on my project"
→ Create .code-method/config.yaml, explain the agent roster and workflow sequence
User: "I have a PRD and architecture done, what's next?"
→ Route to code-stories
User: "Quick bug fix needed"
→ Route to code-dev (quick-dev mode)
Related Skills
ericgandrade/obsidian-frontmatter
testing
VerifiedTrustedCommunity
This skill should be used when the user needs to create, validate, standardize, or repair YAML frontmatter properties in Obsidian notes. Use when the user wants to add or update tags, aliases, dates, custom properties, or any metadata fields in the Properties panel of an Obsidian note.
31SKILL.mdUpdated May 1, 2026
ericgandrade/obsidian-canvas
development
VerifiedTrustedCommunity
This skill should be used when the user needs to create or edit an Obsidian Canvas — a freeform visual workspace that arranges notes, cards, links, images, and web content on an infinite canvas. Use when the user wants to map ideas spatially, build a knowledge dashboard, sketch a concept cluster, or create a visual workspace linking multiple Obsidian notes.
31SKILL.mdUpdated May 1, 2026
ericgandrade/obsidian-automation
tools
VerifiedTrustedCommunity
This skill should be used when the user wants to automate repetitive Obsidian tasks using the Obsidian CLI, shell commands, or scripted workflows. Use when the user needs to batch-create notes, bulk-update frontmatter, run vault maintenance tasks, open specific notes in Obsidian, navigate the vault programmatically, or integrate Obsidian with external tools.
31SKILL.mdUpdated May 1, 2026
ericgandrade/mermaid-diagram
development
VerifiedTrustedCommunity
This skill should be used when the user needs to create, edit, or convert a diagram into Mermaid syntax. Use when the user asks for a flowchart, sequence diagram, class diagram, state diagram, entity-relationship diagram, mindmap, Gantt chart, or any other diagram type that Mermaid supports. Outputs a ready-to-render Mermaid code block.
31SKILL.mdUpdated May 1, 2026