dkpapadopoulos
- 26 skills
- 0 followers
- 4 hours ago last updated
- ▌ Panel · dkpapadopoulos bundleUse to get independent perspectives on one prompt from SEVERAL models — default roster is the strongest available Claude model plus Codex. For ONE other model's opinion or critique use second-opinion instead. Opt-in, phase-agnostic; pairs with synthesize for the merge.
- ▌ Synthesize · dkpapadopoulos bundleUse to combine N independent perspectives on a prompt into one synthesis without forcing consensus. Composition-only — reached from panel's flow or invoked by name.
- ▌ Deploy Gate · dkpapadopoulosUse when preparing to ship or release — before pushing to production, promoting a build, or finalizing a branch — to confirm CI is green, no WIP commits remain, and version and design artifacts are in order
- ▌ Alert Hygiene · dkpapadopoulos bundleUse when facing flapping alerts, alert fatigue, recurring noisy incidents, threshold audits, or SLO-alert redesign questions for a GCP monitoring project.
- ▌ Design Debate · dkpapadopoulosMulti-Agent Debate (MAD) for complex designs — architect, critic and pragmatist who RESPOND TO EACH OTHER, so independence is deliberately not claimed. Use when you want positions challenged and converged. For independent answers with no cross-talk use panel; for ONE other model's opinion use second-opinion.
- ▌ Openspec Ship · dkpapadopoulosUse when shipping a completed feature and generating as-built OpenSpec docs before branch finalization
- ▌ Prototype Lab · dkpapadopoulosProduce 3 thin comparable variants of a proposed design with a comparison artifact and mandatory Human Validation Plan
- ▌ Outcome Review · dkpapadopoulosUse when reviewing a shipped feature's real-world outcome in the LEARN phase — checking adoption, error, or experiment metrics after release, validating ship-time hypotheses, or deciding follow-up work — querying PostHog and creating gated follow-up Jira work
- ▌ Second Opinion · dkpapadopoulosUse when the user wants ONE other model's view — an independent opinion (your prior answer withheld) or a critique of an answer already given (your prior answer deliberately included). One participant. For SEVERAL models answering in parallel use panel; for models arguing with each other use design-debate.
- ▌ Skill Scaffold · dkpapadopoulosUse when creating new skills, commands, or plugins — emits repo-native seed files (SKILL.md skeleton, routing entry, test snippets)
- ▌ Batch Scripting · dkpapadopoulosUse when transforming, migrating, refactoring, or generating across many files at once — codebase-wide renames, 50+ file migrations, mass test/doc generation, framework upgrades — via claude -p with manifest, dry-run, and log-based retry
- ▌ Security Scanner · dkpapadopoulosUse when reviewing code changes for security issues — during REVIEW phase or on explicit security, vulnerability, SAST, or secret-scan requests — running a STRIDE threat-model pre-pass, then available Semgrep/Opengrep, Trivy, and Gitleaks scanners with a self-healing fix loop
- ▌ Agent Team Review · dkpapadopoulosUse when a code change touches 5+ files or modifies auth/secrets/permissions/hooks/CI paths and needs multi-lens parallel review (security, quality, spec, governance) before merge.
- ▌ Capture Knowledge · dkpapadopoulosUse when capturing a durable, team-relevant learning into the committed .claude/knowledge/ base — a gotcha, decision, convention, or runbook worth sharing with teammates' agents. Human-gated.
- ▌ Improvement Miner · dkpapadopoulos bundleUse when mining the repo for improvement proposals in the LEARN phase — manually sweeping eval baselines, gate-status output, memory feedback, and parked revival criteria into a ranked, evidence-graded proposal report with in-session approve/reject and a GitHub-issue queue
- ▌ Incident Analysis · dkpapadopoulos bundleUse when investigating production symptoms — connection failures, pod crashes/restarts, SIGTERM/OOM errors, latency spikes, Cloud SQL/proxy issues, deployment-correlated errors, ImagePullBackOff, CreateContainerConfigError, or node NotReady events
- ▌ Product Discovery · dkpapadopoulos bundleUse when starting a new feature or initiative and you need problem context, prior art, and acceptance criteria before design — the DISCOVER phase entry point — pulling Jira/Confluence context and synthesizing a discovery brief to validate problem framing
- ▌ Authorial Judgment · dkpapadopoulos bundleUse when authoring or de-generic-ifying persuasive prose — essays, blog posts, op-eds, newsletters, talks, or a "make this not sound like AI" rewrite — to apply a post-draft authorial-judgment revision pass. NOT for README/API-docs, specs/changelogs, or code.
- ▌ Runtime Validation · dkpapadopoulosUse when you need to prove a change actually works through its real interfaces — during REVIEW or on requests like validate the feature, does it work, run e2e, or smoke test — covering browser E2E, API smoke, CLI checks, and a11y, perf (Lighthouse), and visual-regression audits with graceful tool-degradation
- ▌ Agent Safety Review · dkpapadopoulosUse when a design or implementation involves autonomous agents, unattended/background operation, private-data access combined with external/untrusted input, or outbound actions (sending data, posting, pushing, API calls) — the lethal-trifecta risk
- ▌ Agent Team Execution · dkpapadopoulos bundleUse when executing implementation plans with 3+ independent, file-disjoint tasks that benefit from parallel specialist agents with shared contracts and reviewer-gated completion
- ▌ Project Verification · dkpapadopoulos bundleUse when you need to run the repo's own declared test/lint/type gate locally and emit pass/fail evidence — during REVIEW, before requesting code review, or on a request to run the tests or verify the build — discovering the gate from CLAUDE.md, Makefile, pyproject, or .verify.yml
- ▌ Unified Context Stack · dkpapadopoulos bundleUse when any SDLC phase needs external docs, dependency internals, cross-session memory, or feature specs — provides tiered context retrieval across External Truth (docs), Internal Truth (dependencies), Historical Truth (memory), and Intent Truth (feature specs) with graceful degradation based on installed tools.
- ▌ Incident Trend Analyzer · dkpapadopoulosOn-demand postmortem trend analysis — recurrence grouping, trigger categorization, MTTR/MTTD from canonical docs/postmortems/ corpus
- ▌ Implementation Drift Check · dkpapadopoulosUse when verifying an implementation still matches its spec or plan — during REVIEW or SHIP, or on demand to check drift, confirm you are still on plan, or run a spec check — surfacing spec deviations, unvalidated assumptions, and untested code paths against Intent Truth
- ▌ Supply Chain Investigation · dkpapadopoulos bundleUse when investigating a published supply-chain attack on a registry package (npm, Maven, PyPI, Go, Gradle) — advisory-driven org-wide audit. Triggers on attack-language ("compromised", "malicious", "hijacked", "backdoored", "typosquatted"). NOT for routine CVE scanning — that routes to security-scanner.