Use when creating design diagrams, diagram packs, architecture diagrams, ER diagrams, sequence diagrams, swimlane diagrams, business flows, data flows, deployment diagrams, state…
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec. — from phamlongh230-lgtm/yamtam-engine
Translates a user request or PRD document into a structured Design Spec JSON — theme, color, typography, density, and device type.
Designs systematic investment products with transparent methodology, rebalancing rules, and index construction specifications.
Run Claude Code in autonomous iteration loops until task completion — PRD-based feature development, test coverage improvement, lint fixing, documentation generation, dataset…
Requirements phase — a clarifying, options-first stakeholder interview that removes confusion and assumptions (not a relentless grilling) and produces a validated SRS +…
UI development skill covering design token usage, shadcn/ui + Radix composition patterns, accessibility requirements, anti-patterns catalog, and brand context for…
Systematic approach to implementing features with detailed planning, tracking, and testing. Use when building new features, adding functionality to existing projects, implementing…
Use when the user says "write a spec", "create RFC", "write a PRD", or "document this decision". Writes technical specifications, PRDs, RFCs, and ADRs with clear structure.
Expert guidance for writing Product Requirements Documents (PRDs), helping product managers create clear, actionable specs that align engineering, design, and stakeholders.
Generate Playwright E2E test plan and specification documents from project artifacts (user stories, module models, mockups, specifications).
PRD驱动工作流的决策大脑 - 智能判断何时使用搜索、代码分析、多模型聚合。 作为子Skill被 th-prd-driven-dev-workflow 调用，负责工具选择和策略决策。
Execute DSDS roadmap tickets using dependency-aware, acceptance-criteria-first delivery. Use when selecting the next unblocked ticket, implementing code changes, validating…
Project and feature planning with 4 adaptive phases - Specify, Design, Tasks, Execute. Auto-sizes depth by complexity.
Use when you have aligned ATAC-seq BAM files from Tn5-based chromatin accessibility assays and need to perform footprinting analysis.
Generate FEATURES.md at the repo root by reading CONTEXT.md and docs/adr/, then enumerating the user-facing features the domain implies.
Break a PRD into native GitHub sub-issues attached to the parent PRD. Project-local variant of /to-issues, adapted for this repo's PRD-as-parent + native sub-issues +…
Turn the current conversation context into a PRD and publish it as a GitHub issue that is ready to receive sub-issues from /to-issues-project.
Turn the current conversation into a spec (PRD) and publish it to the project's issue tracker — no interview, just synthesis of what was already discussed, with Laravel test seams…
Validates the SYS→PRD→SW requirement traceability chain by reconciling database entries with code docstring tags.
Analyse accessibility tradeoffs when a design decision improves accessibility for one group but may affect another, or when accessibility competes with other requirements.
Use Task Master AI when an agent needs to turn a product request or PRD into a dependency-aware task graph, expand or scope tasks, and keep implementation work anchored to an…
Use Spec Kit when an agent should turn a feature idea into a spec-first workflow with explicit artifacts, planning steps, and task breakdowns before code is written.
Generate PRDs, implementation plans, validation loops, issue investigations, and autonomous fix cycles inside Claude Code before coding starts.
Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy.
Validate and improve an implementation plan in plan mode by cross-checking with docs/design/*.md, docs/ROADMAP.md, docs/requirements.md, and src/. Superset of update-design.
Creates a reusable use case specification file that defines the business problem, stakeholders, and measurable success criteria for model customization, as recommended by the AWS…
[METHODOLOGY] User-spec creation through adaptive interview with codebase scanning and dual validation. Preloaded by dev-product-analyst agent.
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
Analyze PRD.md files for quality issues: incomplete sentences, non-existent references, cross-module inconsistencies, contradictory requirements, duplicate roles, design system…
Tag new items in PRD.md files with unique ID codes and validate no duplicate tags exist. Applies to PRD.md documents structured with module sections containing User Stories, Non…
Validate a PRD for completeness, consistency, and implementation readiness. Use when the user says 'validate the PRD', 'review requirements', or 'is the PRD ready for development'.
Initiative-level PRD acceptance gate. Given a PRD ref/URL (GitHub Issue, Linear project/issue, Notion page, Confluence page, or JIRA issue), resolves the source vendor, reads the…
Use when you have a spec, feature request, or set of requirements that needs to be broken into vibe-kanban issues - decomposes the spec into an issue tree with dependencies,…
End-to-end pipeline that transforms an undocumented vibe-coded prototype into a Spec Kit-compatible specification package and a Superpowers-ready implementation handoff, including…
Clarify intent and freeze requirements by entering the canonical vibe runtime with a discovery-first bounded stop.
Lightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`.
Browser-based visual companion for brainstorming sessions — showing mockups, wireframes, diagrams, and side-by-side comparisons.
Examines a specific product's detailed page to verify it matches the user's requirements, checking price, description, features, and reviews.
Evaluates product listings against user requirements such as price limits and feature matches to identify viable options.
Use when gathering or interpreting requirements, estimating effort, or communicating with stakeholders/customers about what to build
Primary pipeline shaping step after /research and before /prd-to-issues. Use when the problem is understood well enough to turn into a bounded PRD issue.
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build — from…
Draft, critique, or rewrite PRDs (product requirements / product specs) and adjacent artifacts (PR/FAQ, acceptance criteria, rollout plan).
Use when drafting, rewriting, or reviewing a product definition or product design document — the artifact that states what a product is, what problem it solves, who it is for, and…
Guides effective user story creation for software projects covering story templates (As a.../I want.../So that...), common mistakes, technical requirements to story conversion,…
This skill helps users extract structured product listings from Amazon, including titles, ASINs, prices, ratings, and specifications.
Build a structured evidence bank mapping the candidate’s job history to the JD core requirements and identify gaps with mitigation strategies.
This skill should be used when the user says "feature spec", "arness code feature spec", "arn-code-feature-spec", "spec this feature", "help me spec", "design this feature",…
This skill should be used when the user says "arness code plan", "arn-code-plan", "plan this", "write a plan", "create plan", "implementation plan", "plan feature", "plan the…
This skill should be used when the user says "standard", "standard mode", "standard implementation", "arn-code-standard", "standard change", "medium change", "standard feature",…
This skill should be used when the user says "swift", "arness code swift", "quick change", "small change", "just do this", "quick feature", "quick implementation", "swift fix",…
This skill should be used when the user says "feature extract", "arn feature extract", "extract features", "feature backlog", "create backlog", "list features", "what features do…
Use when after computing expected accessibility from filtered peak and sample counts, and before computing final deviation scores.
This skill should be used when the user asks about "BFSG", "Barrierefreiheit", "Barrierefreiheitsstärkungsgesetz", "accessibility audit", "WCAG", "barrierefrei", "Web Content…
This skill enables Claude to analyze capacity requirements and plan for future growth. It uses the capacity-planning-analyzer plugin to assess current utilization, forecast growth…
Expert India Digital Personal Data Protection Act, 2023 (DPDPA) compliance advisor. Use this skill whenever a user asks about the DPDPA, DPDP Act, DPDP Rules 2025, India — from…
Expert India Digital Personal Data Protection Act, 2023 (DPDPA) compliance advisor. Use this skill whenever a user asks about the DPDPA, DPDP Act, DPDP Rules 2025, India — from…
Guide iterative specification and CDC (Cahier Des Charges) creation through deep questioning, context analysis, and proactive proposals.
Orchestrate complete or partial feature implementation workflow with configurable phases. This skill should be used to run the full workflow (specification → research → plan →…