// SDLC workflow with MCP tools. Triggers on "start", "implement", "work on", or unclear workflow.
| name | dev-workflow |
| description | SDLC workflow with MCP tools. Triggers on "start", "implement", "work on", or unclear workflow. |
| Phase | Tools |
|---|---|
| Intake | mcp__linear__get_issue, mcp__notion__notion-search |
| Explore | mcp__memory__search_nodes, mcp__github__search_code, mcp__context7__query-docs |
| Plan | mcp__linear__create_issue (subtasks), mcp__notion__notion-create-pages, mcp__github__create_branch |
| Code | mcp__context7__query-docs, Read, Write, Edit |
| Test | Bash (make test, npm test), /quick-test |
| Deploy | mcp__github__create_pull_request, /smoke-test |
| Improve | mcp__memory__create_entities, mcp__linear__create_issue |
| Change Type | Path |
|---|---|
| New feature, breaking change, architecture | OpenSpec → /openspec:proposal |
| Bug fix, config, tests, typo | Quick → TodoWrite |
Intake: Fetch Linear issue, search Notion for context
Explore: Search Memory for learnings, explore codebase, check related PRs
Plan: OpenSpec proposal OR TodoWrite, create branch
Code: Follow tasks, use platform rules, mark todos complete
Test: /quick-test, add tests for new logic
Review: /code-review, /security-scan if auth/data
Commit: /commit with type: description
Deploy: Create PR, run smoke tests after merge
Improve: Store learnings in Memory, create improvement tasks if needed
# Backend
cd backend && make test
cd backend && make build
# Web
cd web && npm test
cd web && npm run build
# iOS
cd mobile/ios && make test
# Android
cd mobile/android && ./gradlew test
Proactive code quality review. Triggers on significant code changes to check security, performance, architecture, and project patterns.
Capture learnings after tasks. Triggers on task completion, repeated mistakes, retrospective requests, or "what did I learn".
Git workflow management. Triggers when creating branches, preparing PRs, or managing merge decisions.
Proactive OpenAPI workflow. Triggers when OpenAPI spec files are modified to validate, regenerate code, and verify builds.
Proactive security scanning. Triggers when modifying auth, API endpoints, user data, or sensitive operations.
Systematic debugging with 4-phase root cause analysis. Triggers when bugs are reported, errors encountered, or unexpected behavior observed.