By jayteealao
One command — `/wf`, the single SDLC entry point — driving a 10-stage lifecycle from intake through retro, with per-slice artifacts, runtime-truth verification, and PO-confirmed stack fingerprinting. 21 keys: the stages, standalone/drivers (design, probe, simplify, auto, yolo), navigation (status, recap), lifecycle (close), and routers (ship-plan, docs, observability). Code review is the `/wf review` key; design is `/wf design`; observability foundation is `/wf observability`; quick/standalone flows are `/wf intake` modes plus the `/wf probe` and `/wf simplify` keys.
Write or review documentation using the Diátaxis framework. Use when the user asks for a tutorial, how-to guide, technical reference, explanation/conceptual doc, README, a documentation plan, or a review/audit of existing docs. Classifies the request into the right quadrant and enforces boundary discipline between them (learning vs task vs lookup vs understanding). For documentation produced as a stage of an /wf lifecycle workflow, use /wf docs instead.
Consult external models as READ-ONLY oracles — plan critique, code/implementation review, design analysis, diagnosis, second opinion. Fans out to all available providers by default (codex, claude, gemini, openai; a provider keyword narrows to one). Returns a panel of opinions and never edits the repo. The model may invoke it autonomously when a second opinion adds material value; model-initiated runs pin a free subscription CLI (codex/claude).
Generate images from a text prompt. Fans out to all available providers by default (built-in image_gen, gpt-image-2, nano-banana) → a variant set; a provider keyword yields one. Supersedes the imagegen skill. Internal to `/wf design`; not user-invocable.
Fetch and read real upstream source code — from Git hosts (GitHub/GitLab/Bitbucket) and from installed dependencies (node_modules, ~/.m2, Gradle/Android SDK sources, Go/Rust/.NET/Ruby/PHP/Swift/Dart caches) — into a gitignored .scratch/ so you build knowledge from actual code instead of guessing at APIs. Use when a task depends on how a library, framework, package, or SDK actually behaves, when reading a dependency's implementation or types would remove guesswork, when reproducing an upstream bug, or when the user asks to pull down / study / vendor a repo or package source. Reads are read-only and never enter the repo's own git history.
Prototype a UI component/screen from a prompt. Fans out to Stitch + an LLM by default (side-by-side); a provider keyword yields one. Writes a self-contained, sandboxed HTML fragment. Internal to `/wf design`; not user-invocable.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Executables (bin/) — files in this plugin's bin/directory are added to the Bash tool's PATH while the plugin is enabled.
A plugin marketplace with Claude Code plugins, generated Codex adapters, and handwritten Codex-native workflows.
Add this marketplace to Claude Code:
/plugin marketplace add YOUR_USERNAME/agent-skills
Then install available plugins:
/plugin install sdlc-workflow
Codex discovers plugins from the workspace marketplace at .agents/plugins/marketplace.json.
sdlc-workflow exposes generated Codex adapters beside its canonical Claude source.sdlc-workflow-codex is a separate handwritten Codex-native rewrite with no generated adapter layer.To refresh the Codex artifacts for sdlc-workflow:
node scripts/generate-codex-plugin.mjs sdlc-workflow
| Plugin | Category | Description |
|---|---|---|
| sdlc-workflow | workflow | Canonical SDLC workflow with generated Codex adapters |
| sdlc-workflow-codex | workflow | Handwritten Codex-native software delivery workflows |
To add a new plugin:
plugins/your-plugin-name/.claude-plugin/plugin.json, .codex-plugin/plugin.json, or bothnode scripts/generate-codex-plugin.mjs <plugin-name>MIT
npx claudepluginhub jayteealao/agent-skills --plugin sdlc-workflowPersonalized coding tutorials that use your actual codebase for examples with spaced repetition quizzes
AI-powered development tools. 19 agents, 10 commands, 8 skills, 3 MCP servers for code review, testing, documentation, brainstorming, and refactoring workflows with semantic code search.
Reusable skills for SDLC planning, software delivery, development workflows, research, data work, and office productivity.
Language-agnostic development process harness implementing the Stateless Agent Methodology (SAM) 7-stage pipeline with ARL human touchpoint model and Voltron-style language plugin composition. Provides orchestration, workflows, planning, verification, and testing methodology that any language plugin can compose with.
24 agent definitions, 81 reusable skills, 28 lifecycle hooks for GitHub Copilot CLI workflows
Autonomous multi-agent development framework with spec-driven sprints and convergent iteration
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
Software development lifecycle automation - slash commands, agents, and GitHub/GitLab webhook watchers