Product & Planning

j4flmao Bundle

Use this skill when designing microservices architecture — decomposition, communication, data, discovery, observability, deployment. This skill enforces: bounded context decomposition, database-per-service ownership, saga patterns for distributed transactions, strangler fig migration. Do NOT use for: monolith application design, frontend architecture, single-service API design.

j4flmao Bundle

Use this skill when asked about blockchain project management, DAO governance, multi-sig operations, treasury management, tokenomics design, and web3 project methodology. Languages: Solidity, TypeScript, Python. Covers DAO governance frameworks (Compound Governor, Aave, Snapshot, Tally), multi-sig wallet operations (Gnosis Safe, Timelock, proposal lifecycle), treasury management (vesting, streaming, diversification, yield), tokenomics design (supply schedule, inflation, staking rewards, emission curve), and web3-specific project methodology (audit-first, progressive decentralization, community governance). For standard management practices (agile, scrum, kanban, risk management, stakeholder management, OKR/KPI), reference shared skills from skills/management/. Do NOT use for: standard project management (use skills/management/pm), team operations (use skills/management/agile-scrum-kanban), cost analysis (use skills/management/cost-benefit), or technical blockchain development (use other blockchain-* skills).

itsual Skill

Apply MEDDICC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition) to qualify and advance complex deals. Use when selling into multi-stakeholder B2B deals that need rigorous qualification and deal control.

itsual Skill

Write clear Product Requirements Documents (PRDs) that define the problem, goals, scope, requirements, and success criteria for a product or feature. Use when specifying what to build, aligning product/design/engineering, or creating the source of truth for a delivery effort.

itsual Skill

Run structured product discovery to reduce uncertainty about customer problems, solutions, and viability before heavy investment. Use when exploring new opportunities, validating ideas, or deciding whether to build, pivot, or kill a concept.

itsual Skill

Write effective user stories and acceptance criteria that communicate intent, value, and testable outcomes to delivery teams. Use when breaking work into backlog items, refining stories, or improving collaboration between product, design, and engineering.

itsual Skill

Design search experiences that help users find content and actions quickly through query, results, filters, and empty states. Use when building or improving product search, filtering, or discovery interfaces.

itsual Skill

Run effective discovery conversations that uncover pain, impact, stakeholders, and fit — before pitching solutions. Use when preparing for or improving qualification and discovery calls with prospects.

joshuashepherd Skill

Place generated images into real-world context mockups — laptop screens, phone frames, book mockups, poster frames, billboard mockups. Use for marketing previews, social media content, and stakeholder presentations.

concertonotes Skill

Initialize project governance files through the RoadmapSmith CLI.

concertonotes Skill

Run the one-command Zero Mode workflow through the RoadmapSmith CLI.

concertonotes Skill

Run the sync-plus-audit workflow through the RoadmapSmith CLI.

concertonotes Skill

Inspect evidence-backed roadmap validation through the RoadmapSmith CLI.

testdouble Bundle

Analyzes an existing codebase using strategic Domain-Driven Design to discover bounded contexts, surface ubiquitous language and semantic collisions, find places where code boundaries diverge from domain boundaries, and produce an evidence-backed domain and context map. Use when the goal is DDD-specific: bounded context discovery, ubiquitous language analysis, domain model discovery, or mapping contested ownership and responsibility. The entire repository is a valid scope; no module or directory must be named first. Does not assess architectural coupling, cohesion, or technical debt — use architectural-analysis. Does not design service communication, integration patterns, or deployment topology — use architectural-analysis or plan-a-feature. Does not refactor code, diagnose bugs, or review code quality — use refactor, investigate, or code-review.

testdouble Bundle

Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, decide, or nail down an interface, contract, signature, or API change for a capability you can already describe, sized for roughly one pull request. Produces a design document and changes no code. Does not specify what a feature should do — use plan-a-feature. Does not plan delivery or sequencing — use plan-implementation. Does not assess the architecture of existing code — use architectural-analysis. Does not write the code — use tdd. Does not restructure existing code — use refactor. Runs its rounds without pausing for review; to review each round as it lands, use pairing.

testdouble Bundle

Performs a gap analysis between two artifacts (a current state and a desired state) and produces a plain-language, stakeholder-readable report indexed by stable gap IDs. Use when the user wants to compare, evaluate, audit, or reconcile one artifact against another. Does not investigate runtime bugs — use investigate. Does not assess module-level architecture — use architectural-analysis. Does not research open-ended options with no second artifact to compare against — use research.

testdouble Bundle

Discovers the core attributes of the current code repository and its projects — languages, frameworks, tooling, and where things live — and writes a concise reference section directly into the project's AGENTS.md or CLAUDE.md for other skills, agents, and hooks to consume. Use when scanning, analyzing, or detecting the project's technology stack, build tools, or repository structure. Does not create or update project documentation — use project-documentation for writing feature or system docs.

testdouble Bundle

Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.

testdouble Bundle

Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.

itsual Skill

Break complex work into small, verifiable tasks with clear acceptance criteria. Use whenever starting a non-trivial feature, refactor, or project, or when the user asks for a plan, task list, breakdown, or roadmap of implementation steps. Prefer this skill before writing significant code.

itsual Skill

Write engaging internal or external newsletters and periodic updates that people actually read. Use for company updates, product newsletters, team digests, or stakeholder communications.

itsual Skill

Evaluate product opportunities for desirability, feasibility, viability, and strategic fit before committing significant resources. Use when sizing new ideas, comparing bets, or deciding whether an opportunity deserves discovery or delivery investment.

itsual Skill

Apply structured prioritization methods (RICE, value vs effort, MoSCoW, Kano, opportunity scoring, etc.) to make transparent, defensible product trade-offs. Use when ranking roadmap items, features, bugs, or opportunities under constrained resources.

masharratt Bundle

CFN Backlog Management Skill

masharratt Bundle

Agent Discovery Skill

rulebase-co Skill

Use to govern auto-fail criteria so every recorded failure has an owner, SLA, evidence trail, and closure — not a backlog auditors will cite. Trigger for "auto-fails nobody actions", "QA compliance failures sitting open", "hard fail vs soft fail", auto-fail backlog audit, regulatory QA findings, or designing workflow for zero-score evaluations.

tinh2 Skill

Turn a pile of bugs, issues, and error reports into a ranked, actionable plan with reproduction evidence. Triggers: you say "triage these bugs", "prioritize the backlog", "which bugs should we fix first".

tinh2 Skill

Full-spectrum product research pipeline. Runs competitive analysis, technology trend scouting, user feedback analysis, and feature ideation. Triggers: on: research, competitive research, market research, feature discovery, what should we build next.

tinh2 Skill

One-time autonomous design context discovery. Scans the codebase to extract design tokens, typography, colors, spacing, brand patterns, and tech stack, then writes a Design Context section to CLAUDE.md..

tinh2 Skill

Competitive intelligence and market positioning analysis. Researches competitors, compares features, pricing, and tech stacks, then produces a prioritized gap analysis with actionable roadmap..

tinh2 Skill

Project-aware skill discovery and installation. Scans the current repo for stack signals and pain points, searches the skills-hub registry and local ~/.claude/skills, scores candidates on relevance, quality, and maintenance, dedupes against what is already installed.

tinh2 Skill

Turns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Triggers: you hear: write a PRD, turn this idea into a spec, product requirements, I have an app idea, formalize this feature.

testdouble Bundle

Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.

projectious-work Bundle

Create, transition, query, and link WorkItems — tasks, stories, bugs, epics. Use when the user asks to add, update, query, or link work items — backlog items, tasks, bugs, user stories, or epics.

projectious-work Bundle

Create, transition, query, and link WorkItems — tasks, stories, bugs, epics. Use when the user asks to add, update, query, or link work items — backlog items, tasks, bugs, user stories, or epics.

projectious-work Skill

Generates clear, structured status updates for stakeholders — from project context, backlog state, or a brief description of recent work. Use when asked to write a status update, weekly report, progress summary, or team briefing about a project or initiative.