Product & Planning

spielewoy Skill

L4 terminal leaf - RE-ANCHOR. Confirms mission and roadmap frontier alignment after resume or compaction using the three-file governance state.

spielewoy Skill

L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.

spielewoy Skill

L3 roadmap synthesizer/repair author - merges retained scout evidence into the one canonical executable ROADMAP.md and repairs only rejected items; does not spawn.

benjaming Bundle

Create autonomous iterative loops (Ralph Wiggum pattern) for multi-step tasks. Use when setting up automated workflows that iterate over a backlog of tasks with clear acceptance criteria. Triggers on requests like "create a ralph loop", "set up an iterative agent", "automate this migration", or "create an autonomous loop".

cognyai Bundle

Build a portable brand-kit.json for the user's product — colors, typography, voice — that other skills (video, ad creative, landing page) can consume. Multiple discovery paths so it works whether the user has access to their site's source code or only a public URL or just a logo image.

spielewoy Skill

L4 blind fresh verifier - independently checks a candidate roadmap or plan against the exact mission and repository; APPROVE/REJECT, default-FAIL.

spielewoy Skill

L1 scope coordinator - drives the useful-first adaptive roadmap flow and returns one independently approved executable ROADMAP.md before build.

spielewoy Skill

L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.

mhylle Bundle

Tasktracker-native project-wide parallel audit using the Claude Code Workflow tool (dynamic workflows). Partitions a repo / backlog / architecture and fans out read-only agents (one per partition) that return schema-checked findings, aggregates them into a deduplicated, ranked risk register, and OPTIONALLY writes fixes back as tasks under a Bug Fix phase — with all tasktracker writes done by the PARENT, never the parallel agents (single global active-task pointer). Journaled and resumable, so a rate-limit or crash mid-audit resumes without re-running completed partitions. Use for large, embarrassingly-parallel, read/analyze-heavy jobs where each unit is self-contained and the output aggregates — audit every file/component for risk, find all architecture drift (scanArchitectureDrift) or duplicate tasks (detectDuplicates/auditDuplicates), per-file tech-debt sweep, test-coverage or security-surface scan across a whole project. Triggers on "/tt-workflow-audit", "audit the whole repo", "parallel audit", "scan ever

openai Bundle

Use when the user asks which existing accounts to work now, which leads are hottest in a grounded list or pipeline, how to rank a territory, book, pipeline, ICP list, or account list, where to focus this week, or what rep-ready next actions to take. Prioritize accounts using current evidence, suppress or account for in-flight motion, and identify reachable contacts when supported. Use enrichment instead for net-new company discovery or missing-data completion.

openai Bundle

Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions and drafts.

openai Bundle

Use for data-first company, contact, lead, and prospect discovery or enrichment, including firmographic or technographic completion, named-company profiling, entity resolution, ICP matching, prospect-list building, segmentation, trigger or sales-signal analysis, market and territory scans, and enrichment-backed comparisons. Exclude meeting preparation, outreach-led company research, and prioritization of an already established account book.

akornmeier Skill

Convert a rough MVP idea into a demo-grade PRD (Steps 1-7)

artsmc-claude-dev-agents Bundle

Read-only Jira navigation and analytics via the jira-sandbox MCP server (mcp__jira-sandbox__* tools). Use whenever the user asks about Jira in any form — a ticket key like PROJ-123, sprint or backlog status, standup prep, what's blocked, or metrics like velocity, cycle time, and project health. NEVER calls Jira write tools — when the user asks to change Jira (create, comment, transition, sprint moves), use jira-writer instead.

throokie Skill

根据 PRD 文档生成高质量代码实现。使用多代理协作模式，自动创建团队并行开发各层代码，Worktree 隔离上下文，语言专用模型编写。触发词：PRD 转代码、根据 PRD 开发、实现 PRD、PRD 开发、按需求文档编码。

akornmeier Skill

Use when translating PRDs, feature specs, or product requirements into UX specifications for mockup tools like Google Stitch, Figma, or similar. Use before creating visual designs, wireframes, or component specs.

akornmeier Skill

Refine and clarify PRD documentation through structured questioning using the visual AskUserQuestion tool

akornmeier Skill

Use when translating UX specifications into build-order prompts for UI generation tools. Triggers when user has a UX spec, PRD, or detailed feature doc and needs sequential, self-contained prompts for tools like v0, Bolt, or Claude frontend-design.

akornmeier Skill

Transform an OpenSpec change phase into UI-ready build prompts through a 3-step pipeline. PRD generation, then UX specification, then build-order prompts. Use when starting implementation of an OpenSpec feature phase, or when the user mentions "openspec-to-prompts", "feature pipeline", or asks to convert a spec phase to implementation prompts. Requires an openspec change-id and phase number as input.

throokie Skill

PRD 文档树状版本管理，处理需求变更、功能扩展和覆盖逻辑。触发词：更新 PRD、修改 PRD、PRD 版本管理、PRD 树、扩展功能、覆盖需求。

throokie Bundle

将用户需求转换为规范的产品需求文档（PRD）。用户说"生成PRD"、"需求转PRD"、"创建PRD"、"写PRD"或"帮我写个PRD"时立即触发。支持一句话需求、功能清单、用户故事等多种输入形式。PRD 默认保存到项目目录下的 docs/prd/（如果在项目目录中），否则询问用户或保存到全局目录。

throokie Skill

PRD 驱动的完整开发工作流 - 从用户故事分析到自动化测试的端到端流程。 当用户需要"一条龙开发"、"全自动开发"、"从需求到代码"、"先分析PRD再开发"、 "多模型分析后自动开发"、"完整开发流程"、"从需求分析到测试"或任何涉及 PRD分析→需求整合→代码生成→自动化测试的连续工作时，**必须**使用此技能。 整合多模型聚合、Kimi深度整合、PRD生成、多模型代码审查、代码开发、自动化测试等能力。 **新增**: 智能决策大脑(th-workflow-decision-engine) - 自动判断何时使用GitNexus代码分析、 unified-search联网搜索、多模型聚合，测试失败时智能选择修复策略。

throokie Skill

PRD驱动工作流的决策大脑 - 智能判断何时使用搜索、代码分析、多模型聚合。 作为子Skill被 th-prd-driven-dev-workflow 调用，负责工具选择和策略决策。

navraj007in Skill

Convert architecture documents (blueprints, stakeholder presentations) from Markdown to professionally formatted Word (.docx) files. Applies corporate styling, embeds PNG diagrams, and creates presentation-ready documents.

navraj007in Skill

Sync sprint backlog from architecture blueprint to project management tools (Linear, Jira, GitHub Issues, Asana, ClickUp). Creates issues/tasks with user stories, acceptance criteria, priorities, and sprint assignments.

phananhtuan09 Skill

Control Herdr, a terminal multiplexer for coding agents. Use when the user asks to inspect or control panes, tabs, workspaces, terminals, commands, sessions, or communication with another agent, and whenever an orchestrating skill such as foreman-agent needs the Herdr CLI. This skill owns Herdr CLI mechanics; it does not own task backlog policy. Requires HERDR_ENV=1.

phananhtuan09 Bundle

Act as the Foreman for the current repository — own its task and issue backlog in .foreman/, assign work to worker agents through Herdr, track progress, coordinate dependencies, and surface only what needs the human's decision. Invoke with /foreman-agent when opening a session that manages work for this repo. Do not use for executing tasks; a Foreman session never writes production code itself.

navraj007in Skill

Generate presentation-ready Word documents for stakeholder discussions. Translates technical architecture blueprints into business-focused presentations with diagrams, cost analysis, and approval checklists.

helderberto Skill

Create a spec (PRD) through user interview, codebase exploration, and module design. Use when starting a feature with unclear requirements, when the user asks to spec or define what to build, or says "write a spec" or "write a PRD". Don't use when requirements are crisp and a plan already exists (use /plan or /build).

pianzhu Skill

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

kurokeita Skill

Create a developer-focused PRD through user interview, codebase exploration, and module design, then save it under .prd/{prd-name}/ in the current workspace. Use when the user wants to write a PRD, create a product requirements document, plan a new feature, spec out work, or define requirements for implementation. Also trigger when the user says things like "let's plan this feature", "I need a spec for...", "write requirements for...", or "create a PRD for...". Do NOT trigger for: reviewing existing PRDs, creating child tasks from a PRD, or general project management outside the local PRD directory.

kurokeita Skill

Break a local PRD into independently grabbable implementation tasks using vertical slices, then save them under .prd/{prd-name}/tasks/ in the current workspace. Use when the user wants to convert a PRD to tasks, break a spec into actionable work, slice a PRD, or create implementation tasks from a local planning document. Do NOT trigger for: writing PRDs, reviewing PRDs without task creation, or remote work item management systems.

bosh-kuo Bundle

Generate or update a project-level Product Requirements Document (PRD.md) after the user and AI have already discussed requirements, target users, product goals, implementation approach, workflow, and key technical decisions. Focuses on product overview, vision, core objectives, user personas, high-level feature groups, tech stack, system architecture key components, and phased roadmap / future work. Use when the user asks to create a PRD, write a product PRD, document project requirements, summarize the whole project direction, or produce a global project context file for future AI implementation work. Do not use for single-feature specs, acceptance criteria, detailed technical design, or implementation tasks.

wix Bundle

Maps discovered source entities and fields to Wix targets and documents lossiness. Use when creating machine-readable mapping artifacts and review markdown after discovery.

tenequm Bundle

Build with ERC-8004 Trustless Agents - on-chain agent identity, reputation, validation, and discovery on EVM chains. Use when registering agents on-chain, building agent reputation, or using the Agent0 SDK. Triggers on ERC-8004 and Agent0.

masanao-ohba Skill

Invoke when goal-clarifier analyzes user requirements to extract goals and constraints. Provides structured requirement decomposition into functional/non-functional categories, stakeholder mapping, assumption identification, and documentation format.