Our review
This skill describes a complete software development lifecycle (SDLC) workflow using MCP tools like Linear, Notion, Memory, GitHub, and Context7, with phases from intake to continuous improvement.
Strengths
- Clear and comprehensive end-to-end software lifecycle structure
- Task automation via MCP tools (ticket creation, branches, PRs)
- Integration of knowledge management (Memory) and exploration best practices
Limitations
- Requires prior configuration of all MCP tools (Linear, Notion, etc.)
- Workflow is very specific to environments using these tools, not generic
- Can be heavy for simple changes (typo, config) despite the triage
Use this workflow for structured development tasks requiring end-to-end tracking with Linear tickets, Notion documentation, and code reviews.
Avoid this workflow for quick, minor changes (e.g., typo fixes) where a lighter flow would be more efficient.
Security analysis
SafeThe skill describes a standard SDLC workflow using MCP tools for issue tracking, code search, documentation, and testing. Bash usage is limited to running test commands like `make test`, `npm test`, etc., which are common development tasks and not destructive or exfiltrating. No malicious instructions are present.
No concerns found
Examples
start work on feature X: add a search bar to the homepage, reference Linear issue ABC-123, and explore similar implementations in the codebase.work on bug fix for issue DEF-456: login fails on Safari, follow the full SDLC workflow including Notion context, branch creation, tests, and PR.implement a breaking change to the authentication system, using the OpenSpec proposal path with /openspec:proposal and creating subtasks in Linear.name: dev-workflow description: SDLC workflow with MCP tools. Triggers on "start", "implement", "work on", or unclear workflow.
SDLC: Intake → Triage → Explore → Plan → Code → Test → Review → Commit → Deploy → Improve
MCP Tools by Phase
| 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 |
Triage Decision
| Change Type | Path |
|-------------|------|
| New feature, breaking change, architecture | OpenSpec → /openspec:proposal |
| Bug fix, config, tests, typo | Quick → TodoWrite |
Phase Actions
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
Quick Reference
# 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
Anti-Patterns
- Coding without exploring → miss patterns
- Skipping Linear context → untracked work
- No Memory capture → repeat learnings
- Big commits → hard to review
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.