Notre avis
Ce skill décrit un workflow complet de cycle de vie de développement logiciel (SDLC) utilisant des outils MCP comme Linear, Notion, Memory, GitHub et Context7, avec des phases allant de la saisie à l'amélioration continue.
Points forts
- Structure claire et exhaustive du cycle de vie logiciel
- Automatisation de tâches via des outils MCP (création de tickets, branches, PR)
- Intégration de la gestion des connaissances (Memory) et des bonnes pratiques d'exploration
Limites
- Nécessite la configuration préalable de tous les outils MCP (Linear, Notion, etc.)
- Le workflow est très spécifique aux environnements utilisant ces outils, non générique
- Peut être lourd pour des changements simples (typo, config) malgré le triage
Utilisez ce workflow pour des tâches de développement structurées nécessitant un suivi de bout en bout avec des tickets Linear, de la documentation Notion et des revues de code.
Évitez ce workflow pour des modifications mineures et rapides (ex: correction de typo) où un flux allégé serait plus efficace.
Analyse de sécurité
SûrThe 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.
Aucun point d'attention détecté
Exemples
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
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.