Product & Planning

mittuled Bundle

This skill builds and maintains a product risk register that identifies, categorises, and scores delivery, market, and technical risks for an initiative or release. Use when asked to assess risks before committing to a roadmap slot, sprint plan, or go-live decision. Also consider when a project has changed scope significantly and existing risk assumptions may be stale. Suggest when the user is about to approve a launch or major milestone without a documented risk assessment.

mittuled Bundle

This skill ingests, normalizes, and structures qualitative and quantitative product feedback for roadmap review cycles. Use when preparing for quarterly planning or roadmap prioritization. Also consider when a spike in support tickets or churn signals undetected product issues. Suggest when feedback channels exist but no systematic synthesis is feeding product decisions.

npbuilds Bundle

Direct the ethics subdomain — route moral reasoning questions to dilemma analysis, stakeholder mapping, or values excavation. Use when evaluating whether an action is right or wrong, analyzing ethical trade-offs, surfacing hidden value judgments, identifying affected parties, or applying moral frameworks to real-world decisions.

npbuilds Bundle

Orchestrate biotech venture discovery and diligence across frontier target/modality scouting, clinical development, regulatory strategy, asset valuation, competitive intelligence, manufacturing risk, IP analysis, and deal synthesis. Activate when evaluating a therapeutic asset, biotech company, or clinical program — or when scouting which emerging targets and modalities are worth tracking before they become drug classes, and where they sit on the historical mechanism-of-action trajectory. Asclepius reads the question, classifies the discovery or diligence pillar, and routes to the right director.

mittuled Bundle

This skill populates the design backlog with well-defined design tasks aligned to the product roadmap. Use when asked to break down a design brief into backlog items, create design tickets from a spec, or prepare the design backlog for sprint planning. Also consider when the design backlog is empty despite active product initiatives. Suggest when a new design brief arrives without corresponding backlog entries.

mittuled Bundle

This skill extracts and structures functional and non-functional requirements from stakeholder inputs and discovery artifacts. Use when asked to turn interview notes, feature requests, or discovery findings into a structured requirements document. Also consider when a PRD lacks traceable requirements or when scope discussions keep circling without a shared source of truth. Suggest when the user is about to begin sprint planning without a validated requirements set.

mittuled Bundle

This skill constructs data-driven sales proposals with 11 sections including ROI calculations, competitive differentiation, and implementation timeline. Use when asked to build a sales proposal, respond to a pricing request, or create a formal evaluation document. Also consider when prospect requests pricing or formal evaluation. Suggest when opportunity advances past discovery with confirmed budget and timeline.

mittuled Bundle

This skill estimates analytics and data engineering effort for product initiatives. Use when asked to size instrumentation work, estimate dashboard build time, or scope a data pipeline. Also consider when sprint planning requires analytics capacity allocation. Suggest when a PRD is approved without a data workstream estimate.

mittuled Bundle

This skill populates the engineering backlog with well-defined tasks from approved specifications. Use when asked to break a spec into backlog items, seed a project backlog, or create engineering work items from a PRD. Also consider when a phase plan is finalized but no tasks exist yet. Suggest when an approved spec has no corresponding engineering backlog entries.

mittuled Bundle

This skill synthesizes sales signals from prospect conversations into product and positioning insights. Use when asked to analyze field data, produce signal reports, or identify trends from sales conversations. Also consider at end-of-quarter when aggregated deal data is available. Suggest when Product requests field input for roadmap planning.

mittuled Bundle

This skill reviews design deliverables at phase boundaries before progression to the next stage. Use when asked to gate a design between discovery and definition, definition and production, or production and handoff. Also consider when a project is about to transition phases without a formal design quality check. Suggest when a design moves from wireframes to visual design without documented approval.

mittuled Bundle

This skill provides marketing timing input to the product roadmap to align launches with campaign cycles. Use when product is finalizing quarterly roadmap dates, when a launch conflicts with a major campaign or industry event, or when marketing needs lead time guarantees for asset production. Also consider when launches cluster in ways that dilute market impact. Suggest when roadmap dates are set without marketing input.

mittuled Bundle

This skill synthesises post-launch data signals to inform the iteration backlog. Use when asked to analyse post-launch metrics, extract learnings from a release, or prioritize iteration work based on data. Also consider after a feature ships and the team needs data-backed next steps. Suggest when a post-launch review is scheduled without data preparation.

mittuled Bundle

This skill prioritises the design iteration backlog based on user feedback, usability data, and business impact. Use when asked to rank design improvements, triage post-launch feedback into the design backlog, or decide which design debt to address next. Also consider when the iteration backlog has grown without a clear priority order. Suggest when session analysis or accessibility audit findings need to be sequenced for action.

mittuled Bundle

This skill designs end-to-end customer discovery programs -- from hypothesis framing through participant recruitment, discussion-guide authoring, session facilitation logistics, and synthesis methodology. Use when a new product area, feature bet, or market expansion requires direct evidence of customer needs before committing engineering resources. Also consider when existing usage data is ambiguous, NPS commentary flags unmet needs, or a pivot is under evaluation. Suggest when the team is about to invest more than one sprint of effort in a direction that lacks primary customer evidence.

mittuled Bundle

This skill builds and operates the design partner programme to secure early customer input during product development. Use when a new product or major feature initiative needs validated demand and real-world feedback before GA. Also consider when pivoting an existing product and needing fresh signal from a different ICP segment. Suggest when the roadmap contains high-uncertainty bets that would benefit from co-development with customers.

mittuled Bundle

This skill triages incoming support tickets by severity, category, and routing to the appropriate resolution path. Use when asked to classify tickets, set up triage workflows, or route customer issues. Also consider when ticket backlog is growing and routing accuracy is low. Suggest when average first-response time exceeds SLA targets.

mittuled Bundle

This skill writes the instrumentation specification defining what events and properties to track. Use when asked to design an event taxonomy, define tracking properties, or create a measurement plan. Also consider when a new feature enters development without a tracking spec. Suggest when a PRD has success metrics but no corresponding event definitions.

mittuled Bundle

This skill grooms the engineering backlog to ensure tasks are well-defined, prioritised, and sprint-ready. Use when asked to refine tickets, clean up the backlog, or prepare items for sprint planning. Also consider when task descriptions are vague or acceptance criteria are missing. Suggest when sprint planning is approaching and tickets lack detail.

mittuled Bundle

This skill plans customer discovery research including methodology, participant recruitment, and discussion guides. Use when asked to plan user research, set up customer interviews, or design a discovery study. Also consider when a product team is making assumptions about user needs without evidence. Suggest when the user is about to build features based on stakeholder opinions alone.

mittuled Bundle

This skill aligns the platform roadmap with product and engineering roadmaps. Use when asked to prioritize platform work, resolve conflicts between platform and product timelines, or ensure platform capabilities arrive before teams need them. Also consider when product roadmap changes create new platform requirements. Suggest when the user is planning product features without platform readiness review.

mittuled Bundle

This skill operates the ongoing content marketing programme including production, publishing, and distribution. Use when executing the editorial calendar, producing blog posts, guides, or case studies, or distributing content across channels. Also consider when content backlog grows or publishing cadence slips. Suggest when demand gen campaigns lack fresh content assets.

mittuled Bundle

This skill prepares the platform for scale by addressing bottlenecks and single points of failure. Use when asked to assess platform scalability, plan for traffic growth, or eliminate infrastructure bottlenecks. Also consider when the product roadmap includes launches expected to significantly increase load. Suggest when the user is launching a high-traffic feature without a platform scale review.

mittuled Bundle

This skill prioritises the next iteration backlog based on signal synthesis and business impact. Use when the team needs to decide what to build next and multiple competing signals need to be weighed. Also consider when the backlog feels stale or when recent data invalidates previous prioritisation decisions. Suggest when a sprint or iteration boundary is approaching and the backlog has not been re-ranked with fresh signal.

xalgord Skill

Perform coverage-guided fuzzing of compiled binaries using AFL++ (American Fuzzy Lop Plus Plus) to discover memory corruption, crashes, and security vulnerabilities. The tester instruments target binaries with afl-cc/afl-clang-fast, manages input corpora with afl-cmin and afl-tmin, runs parallel fuzzing campaigns with afl-fuzz, and triages crashes using CASR or GDB scripts. Activates for requests involving binary fuzzing, crash discovery, coverage-guided testing, or AFL++ fuzzing campaigns.

xalgord Skill

Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.

codyswanngt Bundle

Decompose a single PRD or specification into ordered work items in the configured tracker. Vendor-agnostic — the source can be a Notion PRD URL, a Confluence PRD URL, a Linear project URL, a GitHub Issue URL, an existing JIRA epic key, a markdown file, or a free-form description; the destination tracker is whatever the project is configured to use via `.lisa.config.json` `tracker` (JIRA, GitHub Issues, or Linear). Single-PRD mode only — for batch scanning of all Ready PRDs in a queue, use the lisa-intake skill.

codyswanngt Bundle

Vendor-agnostic scanner for Ready queues. Notion PRD database URL → first Ready PRD → lisa-plan. Confluence space or parent page URL → first prd-ready PRD → lisa-plan. Linear workspace URL or team key → first prd-ready project → lisa-plan. GitHub repo URL or `org/repo` token → first prd-ready issue → lisa-plan, or first `status:ready` issue → lisa-implement when `tracker = github`. JIRA project key or JQL filter → first Ready ticket → lisa-implement. On the PRD side it also closes the loop: each cycle rolls a ticketed PRD up to shipped and dispatches lisa-verify-prd for one shipped PRD (shipped → verified on pass; on fail, re-opened shipped → ticketed with build-ready fix tickets that auto-build and re-verify — never blocked). Designed as the cron target for /schedule — one eligible item per invocation, exits cleanly on empty. Symmetric counterpart to the single-item lisa-plan and lisa-implement skills.

codyswanngt Bundle

Run the Debrief flow over a shipped initiative. Input: a PRD URL (Notion / Confluence / Linear / GitHub Issue / file), a JIRA epic key, or a GitHub epic issue URL. Output: a triage-ready learnings document covering every work item in the initiative — edge cases, gotchas, process friction, tooling gaps, convention drift — each with structured evidence and a human-disposition field. Persistence is deferred to lisa-debrief-apply.

codyswanngt Bundle

QA failure front door. Takes a human tester's plain-language failure description, finds the right ticket (the served ticket, or the original via duplicate-discovery when the report arrives untied), writes the structured failure report (repro / expected vs. actual / which acceptance criterion failed), diagnoses the EXPECTATION GAP — why the implementing agent's done-evidence said done when QA says it isn't — applies the qa-fail label that makes lisa-rework-triage detection deterministic, and transitions the ticket back to the build-ready status. QA never words a ticket again; agents never guess what QA meant.

codyswanngt Skill

Use when running one cron-safe Lisa repair-intake cycle for stuck or half-closed PRD/build queue items. Delegates to the generated Lisa repair-intake contract, typically with arguments like `github intake_mode=both`.

codyswanngt Bundle

Research a problem space and create a PRD in the configured PRD source. Investigates the codebase, defines user flows, assesses technical feasibility, synthesizes the spec, then creates it in the source (Notion / Confluence / GitHub / Linear per .lisa.config.json `source`) via lisa-prd-source-write — there is no loose document artifact. Vendor-agnostic. Accepts an optional `prd_ready` flag (default false → the PRD is created in the `draft` role; true → created `ready` so lisa-intake auto-claims it) and an optional dedupe `marker`/`dedupe_key` (used when invoked by lisa-project-ideation) so re-runs reference the existing PRD instead of duplicating it.

codyswanngt Bundle

Initiative-level PRD acceptance gate. Given a PRD ref/URL (GitHub, Linear, Notion, Confluence, or JIRA), resolves the source vendor, reads the PRD and its generated top-level child work via the prd-lifecycle-rollup contract, and confirms every required child is terminal before any verification runs — if any is non-terminal it reports the incomplete set and STOPS. When the guard passes it runs spec-conformance against the original PRD requirements plus empirical verification via verification-lifecycle. On CONFORMS with all checks passing: transitions the PRD shipped → verified and posts evidence. On PARTIAL/DIVERGES or any failing check: re-opens the PRD shipped → ticketed (NEVER blocked), creates build-ready fix tickets for each divergence, and posts a product-readable failure report — the fix tickets auto-build, rollup re-ships the PRD, and a later intake cycle re-verifies, so the loop closes itself. Idempotent re-runs: comments regenerate in place via sentinel markers; fix tickets dedupe by stable ref.

codyswanngt Bundle

Update a source PRD with an always-written, machine-readable `## Tickets` (alias `## Generated Work`) section linking back to every work item created from it. Each entry carries a parseable ref + URL + type + parent token so the generated child set is readable without scraping prose. Vendor-aware on the source side (Notion / Confluence / Linear / GitHub Issue / file) and tracker-agnostic on the ticket side; the documented section is written for every vendor, additive to native hierarchy linking. Idempotent — regenerates the section on each run rather than appending, so re-planning never accumulates stale links. Invoked by the *-to-tracker skills at the end of their pipeline and standalone if a PRD's Tickets section needs to be refreshed.

codyswanngt Bundle

Read-only operator surface for the current project's PRD and build backlog health. Resolves the configured PRD source and build tracker from the same Lisa contract used by intake and repair, summarizes lifecycle-role counts, distinguishes idle queues from setup problems, and highlights actionable blocked, in-review, claimed, or shipped work.

codyswanngt Bundle

Configure GitHub Issues as the destination tracker and/or the PRD source for this project. Verifies the gh CLI is installed and authenticated, resolves `org/repo`, scaffolds the build-queue label namespace (`status:*`) when GitHub is the tracker and/or the PRD-lifecycle label namespace (`prd-*` + sentinel) when GitHub is the PRD source, writes the `github` section into `.lisa.config.json`, and offers to set top-level `tracker: "github"` and/or `source: "github"`. Idempotent — re-running updates the existing section and reuses existing labels rather than duplicating. No /lisa:setup:atlassian prerequisite (GitHub auth is standalone).