Plugins

1 plugin

Windows Forensics Toolkit

For digital forensics analysts investigating Windows systems using registry artifacts, prefetch, and event logs.

6 skills · plugin

Results for “artifacts”

16 skills

Guides a structured interview and repository research to clarify feature requirements, classify scope, and produce context artifacts for approval before design.

ux-discovery-artifacts

Creates concise early UX discovery artifacts for PRD development, customer development, new product ideas, feature bets, and redesigns. Use when the user asks to hypothesize an ideal customer profile, generate proto-personas, write customer problem or jobs-to-be-done hypotheses, create journey maps, shape value propositions, or turn product context into design-sprint-style customer insight artifacts for product and engineering teams.

Opens plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.

stakeholder-alignment

Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.

roadmap-communicator

Create clear roadmap communication artifacts for internal and external stakeholders, including presentations, release notes, changelogs, and feature announcements.

20.4k · bundle

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

More results

Generates APEXlang artifacts for Oracle APEX applications using deterministic local-context discovery and compact machine-readable contracts.

Traces design decisions and concepts through session history, handoffs, git, and artifacts, producing a chronological timeline report with citations.

Selects candidate clips from analysis artifacts, applies brief-based must-have and must-avoid rules, and writes a selects_candidates.yaml plan.

Plans sprints, breaks user stories into tasks, and estimates story points from BA and TechLead artifacts, producing sprint plan, task breakdown, and story point files.

Analyzes requirements and produces four artifact files: requirements.md, user-stories.md, acceptance-criteria.md, and business-rules.md, with optional loading from SRS workflow artifacts.

review-roughcut

Reviews a video rough cut by generating deterministic metrics, critiquing the edit against brief and blueprint, and producing review_report.yaml and review_patch.json artifacts.

Reads BA and TechLead artifacts to produce a sprint plan, task breakdown, and story point estimates, creating one tracked todo per sprint task for live pipeline tracking.

Runs a post-launch review of a shipped PRD against its success metrics, interviewing the user on metric movement, assumptions, and decisions, then publishing an outcome-review page to Confluence and updating linked artifacts.

product-strategy-outcome-vision

Creates an outcome-backed product strategy memo from an Ideal Customer Profile markdown file, pasted ICP notes, discovery artifacts, product context, or PRD context. Use when asked to create product strategy, convert an UX Discovery and ICP into strategy, define vision-to-outcome strategy, turn discovery into strategic bets, clarify target customer outcomes, evaluate roadmap strategy, or avoid feature-factory planning.

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.