Claude Skills by Dadmin88

Implement retention and deletion across primary stores, derived data, indexes, logs, queues, caches, exports, backups, and external processors with verifiable completion.

MUST load first for Academy learning or go-learn requests.

Prepare a procurement negotiation from objectives, leverage, evidence, alternatives, tradeable terms, approval limits, and fallback positions without inventing authority.

Assess procurement risk across vendor viability, security, privacy, legal terms, concentration, implementation, continuity, data portability, support, and exit conditions before commitment.

Build a request for proposal that defines business need, scope, requirements, response format, evaluation criteria, evidence, commercial context, timeline, and process so vendors compete on comparable outcomes.

Compare procurement options using total lifecycle cost across price, implementation, integration, migration, training, support, infrastructure, usage growth, switching, exit, and internal operating effort rather than sticker price alone.

Evaluate vendors or tools against requirements, total cost, security, operational fit, contractual constraints, and switching risk.

MUST load first for Academy learning or go-learn requests.

Design product experiences with accessible information hierarchy, semantics, input methods, focus behavior, visual adaptations, content alternatives, and recovery patterns before implementation.

Hand product design to engineering with complete flows, states, responsive and accessibility behavior, component intent, assets, content, constraints, and explicit open decisions while preserving implementation ownership.

Design interaction behavior for a product feature by mapping user intent, controls, feedback, navigation, direct manipulation, interruptions, errors, and platform conventions into a coherent usable flow.

Design an end-to-end product flow from user goal through information architecture, states, interactions, errors, accessibility, and implementation handoff.

Plan a prototype around a specific design or product uncertainty, selecting the minimum fidelity, scope, participants, scenarios, evidence, and success criteria needed to inform a decision.

Design complete product UI states and transitions for normal, empty, loading, permission, validation, error, offline, interrupted, and recovery conditions so the experience remains coherent beyond the happy path.

MUST load first for Academy learning or go-learn requests.

Define acceptance criteria as observable product behavior, states, permissions, boundaries, errors, and outcomes that design, engineering, and QA can interpret consistently without prescribing unnecessary implementation.

Prioritize competing product work using explicit outcomes, evidence, urgency, confidence, effort and opportunity cost without treating scoring frameworks as objective truth.

Reduce product uncertainty before major commitment by framing the problem, identifying risky assumptions, gathering user and market evidence, testing solution hypotheses, and deciding what to build or learn next.

Turn a product problem into scoped requirements, user outcomes, constraints, acceptance criteria, exclusions, and decision-ready tradeoffs.

Define the smallest coherent product scope for a release by protecting the intended outcome, separating must-have behavior from follow-up work, and making exclusions, dependencies, risks, and acceptance explicit.

Make roadmap decisions by connecting product outcomes, evidence, sequencing, dependencies, capacity, uncertainty, and explicit commitments.

MUST load first for Academy learning or go-learn requests.

Produce a concise competitive battlecard focused on customer decision criteria, verified differences, proof, traps to avoid, and honest fit boundaries.

Define an ideal customer profile and prioritized use cases from verified customer problems, buying context, alternatives, and product capability.

Build a launch messaging package that turns shipped capability into audience-specific narrative, proof points, FAQs, objections, and channel-ready message hierarchy.

Create a product positioning brief that distinguishes target customer, category/frame, problem, differentiated value, proof, alternatives, and intentional tradeoffs.

Create sales and solutions enablement with discovery cues, value narrative, technical proof, objection responses, competitive context, and qualification boundaries.

MUST load first for Academy learning or go-learn requests.

Maintain product decision records with problem, evidence, options, owner, rationale, expected outcome, dependencies, revisit conditions, and downstream communication.

Operate a feedback loop that aggregates qualitative and quantitative product signals, preserves provenance, identifies recurring themes, and routes them into discovery/decision processes.

Design a product intake system that captures requests/feedback with source, problem, evidence, affected users, urgency, duplication, owner, and disposition without turning every request into roadmap work.

Design a product operating rhythm that coordinates discovery, prioritization, delivery review, launches, metrics, feedback, and decision follow-through with minimal ceremony.

Measure and improve product-process health through intake age, decision latency, discovery evidence, roadmap churn, launch readiness, feedback closure, and cross-team rework.

MUST load first for Academy learning or go-learn requests.

Analyze whether a product has or could build durable advantage through switching costs, network effects, proprietary data, distribution, brand, scale, ecosystem, workflow embedding, cost structure, or accumulated capability using evidence rather than moat vocabulary.

Assess a product opportunity from customer problem, evidence, market context, strategic fit, alternatives, value, feasibility constraints, risk, and learning cost before committing to a solution.

Prioritize a portfolio of product bets by strategic fit, customer value, evidence, opportunity cost, dependencies, risk, capacity, and learning rather than ranking isolated feature scores.

Develop product strategy by connecting target users, unmet needs, differentiated advantage, capabilities, constraints, sequencing, and measurable strategic bets.

Build a product strategic narrative that connects market change, customer problem, product advantage, choices, capabilities, and measurable direction into a coherent explanation of where the product is going and why.

MUST load first for Academy learning or go-learn requests.

Maintain a dependency map across projects/repos/teams using prerequisite outcomes, interfaces, needed-by dates, owners, readiness evidence, and failure consequences.

Define and run an integration milestone that proves independently developed work combines into one meaningful program outcome.

Structure a multi-project program around outcomes, workstreams, decision rights, dependencies, milestones, governance, and completion criteria.

Coordinate a multi-system or multi-team cutover with prerequisites, freeze points, migration sequence, communication, command roles, rollback/forward recovery, and post-cutover validation.

Operate program-level risk governance for cross-team dependency, sequencing, migration, organizational, supplier, security, and cutover risks with decision triggers.

MUST load first for Academy learning or go-learn requests.

Build a delivery plan with milestones, dependencies, owners, risks, acceptance points, and realistic sequencing.

Track project dependencies as explicit predecessor outcomes, owners, needed-by dates, readiness evidence, and blocking consequences instead of vague links between tasks.

Plan milestones around meaningful integrated outcomes, dependencies, acceptance evidence, and decision points instead of arbitrary calendar checkpoints.

Maintain a project risk register that makes uncertain events, probability, impact, triggers, mitigation, contingency, ownership, and residual exposure visible throughout delivery.