Use when the user asks for conceptual guides, architecture overviews, design rationale, trade-off discussions, background on how a subsystem works, historical context, or "why is it built this way?" documentation. Creates understanding-oriented content that builds mental models — the why, not the how. Do not use for direct task execution (use how-to) or factual lookup (use reference).
From sdlc-workflownpx claudepluginhub jayteealao/agent-skills --plugin sdlc-workflowThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Write understanding-oriented documentation that helps readers see the why, context, trade-offs, and larger picture.
Explanation is not procedure and not reference. It is where reasoning belongs.
Use this skill when the user asks for:
Do not use this skill for direct task execution or factual lookup.
Explanation can include:
Explanation must not drift into:
Use a structure like:
Produce explanation that:
Before returning, verify: