SDLC Workflow with MCP Tools

VerifiedSafe

This skill provides a structured SDLC workflow covering intake, exploration, planning, coding, testing, review, commit, deploy, and improvement. It uses MCP tools like Linear, Notion, GitHub, Memory, and Context7 to manage tasks and context across phases. Helpful when working on features, bugs, or changes in a project with integrated tooling.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#sdlc#workflow#mcp-tools#linear#notion

Recommended for

Automated summary

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
When to use it

Use this workflow for structured development tasks requiring end-to-end tracking with Linear tickets, Notion documentation, and code reviews.

When not to use it

Avoid this workflow for quick, minor changes (e.g., typo fixes) where a lighter flow would be more efficient.

Security analysis

Safe
Quality score85/100

The 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

How this analysis is made

Examples

Implement a new feature
start work on feature X: add a search bar to the homepage, reference Linear issue ABC-123, and explore similar implementations in the codebase.
Bug fix with full workflow
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.
OpenSpec proposal for architecture change
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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sdlc-workflow-with-mcp-tools-mmbiziqo/download' --output '.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo/SKILL.md.part' && mv '.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo/SKILL.md.part' '.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: 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

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo/SKILL.md' && test -s '.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dev-workflow' && cp -R '.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo' '.claude/skills/dev-workflow'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo'

openskills read 'sdlc-workflow-with-mcp-tools-mmbiziqo'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/sdlc-workflow-with-mcp-tools-mmbiziqo/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills