sdlc-skills

In the author's own words, from each skill's SKILL.md — showing the first 30 of 71 files.

• deep-research

  Use when the user asks to 'research trends', 'analyze a topic', 'fact-check this', 'verify claims', 'what's the state of X', or hands you a document to vet. A disk-first, checkpointed research workflow with three modes — trend research, topic analysis, and fact-checking.

  skills/deep-research/SKILL.md on GitHub (opens in a new tab)

• delivery-monitor

  Delivery monitor for harness work items — the cycle-time and cadence sibling of tokenomics. Registers a plan (campaign → mission → task) with ranged, human-accepted estimates, records dispatch/merge/cancel transitions into a git-committed event ledger (.agents/telemetry/delivery/), backfills history from git, and reports cycle time, weekly throughput/velocity and estimate-vs-actual delta per leve…

  skills/delivery-monitor/SKILL.md on GitHub (opens in a new tab)

• gathering-context

  Use when the user says 'what do we know about X', 'find prior discussions with Y', or before drafting any reply where prior history matters. Gathers cross-channel context (local KB, email, Teams, optional web) about a person or topic before responding.

  skills/gathering-context/SKILL.md on GitHub (opens in a new tab)

• knowledge-curation

  Use when promoting a hard-won fact from per-role memory into the shared, committed `.agents/knowledge/` layer, auditing that layer for stale or unindexed notes, or retiring a fact that stopped being true. Also use at the end of a substantial session or mission to sweep memory for anything cross-role worth committing. Not for per-role notes or daily logs (that is the `memory` skill), and not for m…

  skills/knowledge-curation/SKILL.md on GitHub (opens in a new tab)

• memory

  Use when the user says 'remember this' or 'log this', asks 'what did you learn yesterday', or whenever you discover something worth keeping across sessions. Per-role persistent memory — durable facts, preferences, decisions, and a daily log, as plain markdown.

  skills/memory/SKILL.md on GitHub (opens in a new tab)

• microsoft-365

  Use when the user asks to 'check my email/Teams/calendar', 'what meetings do I have', 'any messages about X', or whenever a task needs live Microsoft 365 data rather than memory. Microsoft 365 (Graph) access to email, Teams, calendar, and SharePoint — scriptable scans plus an interactive query.py.

  skills/microsoft-365/SKILL.md on GitHub (opens in a new tab)

• obsidian-vault

  Use when the user says 'save to vault', 'log this note', 'find my notes about X', 'what's in my inbox', 'open loops', or when filing an incoming signal (email/chat/memo) or updating people/project/meeting notes. Headless, file-system Obsidian vault operations, no Obsidian app needed.

  skills/obsidian-vault/SKILL.md on GitHub (opens in a new tab)

• tosca-automation

  Use when the user asks to create a TOSCA test case, run a playlist, organize cases, or perform any TOSCA Cloud REST/CLI operation. Tricentis TOSCA Cloud automation via the bundled tosca_cli.py — create/update/run TestCases, Modules, Reusable Blocks, Playlists, folders, and TSU import/export.

  skills/tosca-automation/SKILL.md on GitHub (opens in a new tab)

• verifying-outcomes

  Use when the user asks to 'verify', 'did this actually work', 'is X really done' — or before you claim a task is complete and before closing an issue or merging a PR. Goal-backward verification — checks whether the desired outcome was achieved, not whether tasks were marked done.

  skills/verifying-outcomes/SKILL.md on GitHub (opens in a new tab)

• visual-testing

  Use when rendered UI needs visual regression checking — "did the UI change", "visual test", "screenshot diff", "compare against the baseline", "catch layout regressions", or a visual assertion in a test run. Works on any HTML you can render — a generated static page (design mock, report, flow-map poster) opened from disk, or a running app driven by your existing browser/device automation. Screens…

  skills/visual-testing/SKILL.md on GitHub (opens in a new tab)

• vividus

  Use when the user mentions Vividus, .story files, vividus-bom/-starter, backtick-parameter BDD, or ./gradlew runStories. Bootstrap, configure, and author tests for the Vividus BDD framework — JBehave-based, config-first .story files spanning web/REST/mobile/DB via 47+ plugins.

  skills/vividus/SKILL.md on GitHub (opens in a new tab)

• xray-testing

  Use when the user says 'pull test PROJ-T42', 'create Xray test from this AFS', 'upload JUnit to test plan', or performs any Xray CRUD. CRUD plus results import on Xray entities (Test, Precondition, Test Set/Plan/Execution/Run) across Cloud (GraphQL) and Server/DC (REST).

  skills/xray-testing/SKILL.md on GitHub (opens in a new tab)

• browser-verify

  Use when you need to run arbitrary JS in a page, inspect cookies/localStorage, check computed styles, emulate devices, or drive real mouse/keyboard events. Chrome DevTools Protocol browser automation with zero external dependencies.

  bundles/feature-development/skills/browser-verify/SKILL.md on GitHub (opens in a new tab)

• bugfix-workflow

  Use when the user says "fix bug", "fix

  bundles/feature-development/skills/bugfix-workflow/SKILL.md on GitHub (opens in a new tab)

• code-review

  Use when the user asks to 'review this code', 'check my changes', 'review PR', 'audit' — and proactively after a non-trivial change or before opening, approving, or merging a PR, even unprompted. Reviews code for correctness, security, performance, and maintainability.

  bundles/feature-development/skills/code-review/SKILL.md on GitHub (opens in a new tab)

• completing-a-task

  Use when a routed task has been implemented and the working code needs to be committed, pushed, PR'd, commented on the issue, and handed to a reviewer. The canonical task-handoff protocol; runs standalone or as the final phase of implement-feature.

  bundles/feature-development/skills/completing-a-task/SKILL.md on GitHub (opens in a new tab)

• git-workflow

  Use when the user asks to "commit", "create PR", "branch", "merge", "rebase", "cherry-pick", "tag", or otherwise manage git history. Guides disciplined git operations — branching, commits, PRs, and recovery.

  bundles/feature-development/skills/git-workflow/SKILL.md on GitHub (opens in a new tab)

• implement-feature

  Use when the user says "implement", "build feature", "work on task", or once a plan or story is approved and you're about to start building. The end-to-end feature-implementation workflow; delegates the final handoff to completing-a-task.

  bundles/feature-development/skills/implement-feature/SKILL.md on GitHub (opens in a new tab)

• issue-tracking

  Use when the user asks to 'create an issue', 'file a bug', 'check issues', 'update a ticket', 'create an epic', or anything about issue or ticket management. Creates, manages, and tracks issues in GitHub, Linear, or GitLab.

  bundles/feature-development/skills/issue-tracking/SKILL.md on GitHub (opens in a new tab)

• plan-feature

  Use when the user says "plan a feature", "design this", "how should we build", or before writing code for any non-trivial feature. Produces an approved task breakdown before implementation begins — plan first, build second.

  bundles/feature-development/skills/plan-feature/SKILL.md on GitHub (opens in a new tab)

• playwright-testing

  Use when a manual-QA agent does live browser testing through the Playwright MCP server — exploring/profiling a web app or executing a web test case against a running app, with no test code generated. Web/PWA/hybrid targets; used by app-profiler and test-runner. Mobile native → use mobile-testing instead.

  bundles/feature-development/skills/playwright-testing/SKILL.md on GitHub (opens in a new tab)

• reproducing-issues

  Use when a bug is unclear or unconfirmed and needs reproduction before RCA or any fix. Turns a vague bug report into precise, repeatable steps with evidence and a CONFIRMED / CANNOT-REPRODUCE / PARTIAL verdict. Reproduction and documentation only — does not fix code.

  bundles/feature-development/skills/reproducing-issues/SKILL.md on GitHub (opens in a new tab)

• root-cause-analysis

  Use when a bug has been reproduced or confirmed and needs its exact cause traced before a fix is proposed, or when the user says 'investigate issue'. Traces a bug to its exact cause in the codebase. Investigation only — reports the cause on the ticket; does not edit code.

  bundles/feature-development/skills/root-cause-analysis/SKILL.md on GitHub (opens in a new tab)

• screen-specs

  Use when screens need designing or documenting as reference a developer or agent can build from — "design the screens", "screen specs", "what should this screen look like", "turn the flows into designs", "document the UI", or when a flow map's nodes need to become actual screens. Produces standalone HTML pages showing each screen as a device-framed mock beside its spec — regions with Material com…

  bundles/feature-development/skills/screen-specs/SKILL.md on GitHub (opens in a new tab)

• seeding-a-project

  Use when the user asks to 'seed the project', 'onboard this repo', 'generate project config', 'create AGENTS.md', or after the scout has explored the codebase. Generates AGENTS.md and .agents/ configuration files for a new project.

  bundles/feature-development/skills/seeding-a-project/SKILL.md on GitHub (opens in a new tab)

• session-retrospective

  Use when asked to run a retrospective, mine past sessions, or improve the team from what already happened — turning prior Claude Code conversations and sub-agent sessions into proposed memory and workflow updates. Used by scout.

  bundles/feature-development/skills/session-retrospective/SKILL.md on GitHub (opens in a new tab)

• test-automation-workflow

  Use when a TMS test case needs to become an automated test, or when automating a regression batch — "automate TC-NNN", "convert this case to Playwright", any flow from a manual case to green framework tests. Pluggable TMS (Zephyr/TestRail/Xray/Azure/markdown).

  bundles/feature-development/skills/test-automation-workflow/SKILL.md on GitHub (opens in a new tab)

• test-case-analysis

  Use when a TMS test case needs manual execution, selector discovery, or defect investigation before automation — "analyse SCRUM-T101", "run this case and emit an AFS", any pre-automation case exploration. Produces an Automation-Friendly Spec (AFS); does not write test code.

  bundles/feature-development/skills/test-case-analysis/SKILL.md on GitHub (opens in a new tab)

• user-flow-maps

  Use when a user flow, journey, or screen-to-screen behaviour needs to become a visual flow map — "draw the flow", "make a flow map", "user flow diagram", "map the screens", "turn these journeys into diagrams", or when acceptance criteria need a picture reviewers can sign off on. Renders a spec of screens, decisions and transitions into standalone HTML posters — numbered screen wireframes, decisio…

  bundles/feature-development/skills/user-flow-maps/SKILL.md on GitHub (opens in a new tab)

• accessibility-audit

  Accessibility and WCAG compliance analysis, from the accessibility snapshot and visual review — flags issues automated axe-style scans miss.

  bundles/manual-qa/skills/accessibility-audit/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• ECCby affaan-m The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Cod… 280k stars · 30 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• andrej-karpathy-skillsby multica-ai A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls. 220k stars · 1 skill
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• ui-ux-pro-max-skillby nextlevelbuilder An AI skill that provides design intelligence for building professional UI/UX across multiple platforms. 136k stars · 7 skills
• graphifyby Graphify-Labs Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Curs… 127k stars · 1 skill