Product & Planning

gordonlu Bundle

Generate a 15s 16:9 hyper-real first-person scientific-expedition documentary short: two volcanologists in anti-slip boots, helmets and headlamps squeeze into a newly formed lava tube on a misty volcanic wasteland at dawn (5:30–5:45) to record it before its structure changes further — entry, wall reveal, steam anomaly discovery, cautious check, marking and retreat toward the mouth-light. Use when the user wants a first-person expedition / cave-inspection documentary, a "threshold crossing into an unstable structure" scene, or a realistic scientific survey short — T2VA (pure text generation, no reference image). Hard rules: rock walls must read as real solid volcanic rock (not props), natural light diffusion, no fantasy, no supernatural, no impossible cave geometry, calm professional demeanor, breathing and footsteps always audible.

trogonstack Skill

Review Product Overview Documents for completeness, clarity, source-of-truth conflicts, module-boundary drift, and likely downstream FRD / Blueprint / Work Order impact. Reads the default and custom files under `.trogonai/project/{projectid}/prd/` and writes a review. Use when the user asks to review, audit, critique, or sanity-check a PRD.

trogonstack Bundle

Draft the Personas of a PRD by defining the users, their goals, and what success looks like for them. Drives discovery through who the users are, the jobs they are trying to do, their constraints, and the per-persona definition of success. Writes to `.trogonai/project/{projectid}/prd/personas.prd.md`. Use when the user wants to define or sharpen who the product is for.

trogonstack Bundle

Draft the Current State of a PRD by documenting the status quo the product improves upon. Drives discovery through what users do today, the workarounds in use, the costs of the status quo, and the alternatives that already exist. Writes to `.trogonai/project/{projectid}/prd/current-state.prd.md`. Use when the user wants to document the baseline before proposing a change.

trogonstack Bundle

Draft an additional Product Overview Document beyond the six defaults when a product-specific context area is needed. Keeps custom PRDs at product-level why/what, prevents duplicate default sections, and writes to `.trogonai/project/{projectid}/prd/{slug}.prd.md`. Use when the user needs a custom overview document rather than a feature requirement.

trogonstack Skill

Initialize a new project with the six default Product Overview Documents (business problem, current state, personas, product description, success metrics, technical requirements). Scaffolds stubs and walks the user through running each section skill in priority order. Use when the user is starting a project and there are no PRD files yet.

trogonstack Bundle

Draft the Success Metrics of a PRD by defining the key metrics used to measure success. Drives discovery through the primary outcome metric, leading indicators, guardrail metrics that must not regress, and the instrumentation source for each. Writes to `.trogonai/project/{projectid}/prd/success-metrics.prd.md`. Use when the user wants to define how success will be measured before building.

trogonstack Bundle

Draft the Business Problem of a PRD by framing the core problem the product addresses, the gaps in today's tools and processes, and why change is necessary now. Drives discovery through who experiences the pain, what fails today, and the cost of inaction. Writes to `.trogonai/project/{projectid}/prd/business-problem.prd.md`. Use when the user wants to write, refine, or audit the problem framing of a product or feature.

trogonstack Bundle

Draft the Product Description of a PRD by describing what the product is and how its parts fit together. Drives discovery through the one-liner, the user-facing surfaces, the major components, how they interact, and the boundaries of what the product is not. Writes to `.trogonai/project/{projectid}/prd/product-description.prd.md`. Use when the user wants to describe the product shape without diving into requirements.

trogonstack Bundle

Draft the Technical Requirements of a PRD by capturing the technical constraints and requirements the product must meet. Drives discovery through performance, scale, reliability, security, privacy, compliance, integrations, platforms, accessibility, and localization. Writes to `.trogonai/project/{projectid}/prd/technical-requirements.prd.md`. Use when the user wants to capture the non-functional and platform constraints engineering will design against.

trogonstack Skill

Apply the shared Requirements operating model across product-requirements skills: Requirements / Blueprints / Work Orders boundaries, single source-of-truth ownership, TrogonStack ask-question-compatible clarification, Product Overview / FRD scope, feature hierarchy, and downstream impact. Use alongside PRD or FRD writing, review, split, or getting-started work when cross-document consistency, ambiguity, or module handoff matters.

karlorz Bundle

Read-only audit of Claude-to-Cursor plugin discovery and SkillWiki cache freshness. Use to exam or diagnose those packs.

karlorz Bundle

Turn architecture analysis into a PRD or spec without interviewing. Use after codebase-architecture-analyze or for a feature spec.

mattforni Bundle

Groom a Linear team's queue. Two modes, cycle grooming (when the team runs Linear cycles, trim the active cycle to a realistic slate) and backlog grooming (when the team has a backlog without active cycles, triage by priority, staleness, and intent). Use whenever the user mentions Linear grooming, triaging issues, pruning a backlog, sprint grooming, "the cycle is overstuffed", "let's clean up the queue", "groom the backlog", or wants to make decisions across many issues at once. All Linear access goes through the `linear` CLI.

mattforni Bundle

Direction-setting session for a venture. First-principles positioning (Dunford), adversarial critique walked one finding at a time, brand and naming decisions, a multi-fidelity roadmap, and full artifact true-up (docs, Linear, calendar, Todoist). Use this skill whenever Forni wants to plan a business's direction, asks "what is this business", wants to work through positioning or strategy from scratch, questions whether the ladder is against the right wall, wants a brand or naming workshop, or invokes "/assist:plan-venture". Also trigger for a Monday planning block that turns strategic ("direct the energy before scheduling more work"). Weekly slotting stays in assist:plan-week; this is the deeper, occasional session that decides what the weeks are for.

nixopus Skill

MCP server discovery, tool invocation, and provider catalog integration. Load when a task involves external services, third-party tools, or when the user asks about MCP servers.

nixopus Skill

Deploy multi-service monorepo applications — service discovery, dependency ordering, shared build contexts, selective deployment, and compose generation. Use when the repository contains multiple deployable services, apps, or packages.

nonlinear-xyz Skill

Dev standup — open Linear tickets grouped by in-flight, top priority, and backlog

paulkinlan Skill

Identify stakeholders and map their influence, interest, and communication needs

oimiragieo Skill

Use when planning, building, reviewing, or prioritizing any slice of the world-class roadmap — the agentic EDIT-CONTROL PLANE thesis (not faster grep); the S1 fail-closed edit tickets + verify-edit with ESCROWED CI-held-key evidence; S2 registration-aware impact-diff; S3 next_action protocol; S4 warm-session resume; S5 head-bound escrowed evidence chain; S6 semantic default + why_ranked; S7 federated workspace object; or the H1 unknown-command/PATH-honesty prerequisite. Triggers: "edit-control plane", "world-class", "verify-edit", "escrowed evidence", "S1..S7", "edit tickets", "CI-held signing key", "semantic blast radius", "impact diff", "next_action protocol", "federated workspace", "why_ranked". Covers the council-amended spine (design + prioritization contracts), the banked-vs-new status of each item, the both-front-door + 4-site registration obligations, and the gate sequence (change-control → thinktank design council → TDD) every slice must pass. NOT a build plan — build routing happens through tensor-g

oimiragieo Skill

Use when shipping an AUDIT-FIX PR for a verified H/M finding, running or resuming the codex-gated adversarial audit loop for a fix (behavioral RED -> minimal fix -> independent codex gate -> verify every finding with your OWN probes -> re-audit until SHIP), writing a gated test that must pass identically on the dev desktop AND the CI pytest env, or any security-surface change that needs an adversarial gate before merge (A3). Also when a prior fix to the same finding already shipped wrong (the twin law). Triggers: "codex-gated", "audit loop", "FIX-FIRST", "SHIP", "audit-fix PR", "adversarial gate", "try to BREAK it". Distinct from the pre-build plan council (tensor-grep-backlog-campaign) and the change gates (tensor-grep-change-control): this is the per-item fix loop itself. Not for first-pass feature planning or merge/release administration.

oimiragieo Skill

Use when building, extending, or reviewing tensor-grep's APPROVED local hybrid semantic search — BM25 + CPU dense embeddings fused with Reciprocal Rank Fusion (RRF), no API key, no GPU (roadmap item #1). Load before adding a dense/embedding leg, RRF fusion, a `tg index` command, or changing `tg search --rank` / `--bm25`. Covers the decision-gated build phases with exact commands + expected gate numbers, the ranked solution menu (Semble / ripvec / BM25-only) with derivation obligations, the retrieval-quality + editor-plane + token-economy promotion gates, the Backend Fail-Closed Contract for the dense leg, fenced-off wrong paths (no API-key embeddings, no GPU dependency, do not break `--format rg` / `--json` / `--ndjson` semantics), and routing promotion through change-control. STATUS as of 2026-07-08, v1.49.3: the dense leg + RRF fusion described here as the target architecture (Candidate 1 / the Semble pattern) SHIPPED as `tg search --semantic` (`retrieval_dense.py` + `retrieval_fusion.py`, default-OFF, gate

oimiragieo Bundle

Use when demand is SATISFIED but product code is not yet authorized: writing or auditing docs/requirements+design+decisions packets, recording skip-Fable waivers, splitting PERF vs HONESTY sub-dispositions, or resisting "design on main = shipped" (A117/A122). Covers the authorization ladder (measure → design packet → Sol exact-commit → optional Fable waiver → deliberate build go → TDD+A3), measurement-envelope timeouts (A120), backlog+R7 pairing when raising request_queue_size under ThreadingMixIn (A121), and Sol audits that hash exact commit bytes. NOT for demand measurement itself (tensor-grep-demand-gate-measurement) or unconstrained product builds without a recorded go.

stefan-stepzero Bundle

Prioritize which specs to write first from product + engineering definitions. Triggers: 'spec roadmap', 'what to spec first', 'prioritize features', 'spec backlog'.

stefan-stepzero Skill

Internal reviewer — assesses planning artifact alignment. Checks definitions agree, specs cover roadmap, no gaps. A per-unit reviewer invoked by a caller (the engine in steered mode or a direction/planning caller), not for direct use.

stefan-stepzero Bundle

Use when defining users, personas, or user journeys. Triggers: 'who are users', 'create personas', 'user research', 'user stories'.

gtrabanco Bundle

Found or continue a roadmap autopilot one stage per invocation. Default: human merge. --fullauto is invocation-scoped and uses the transient wrapper only after a fresh audit. Triggers: "ship-roadmap", "ship the roadmap", "autopilot this project".

gtrabanco Bundle

Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row `folded: yes` updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".

gtrabanco Bundle

Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".

gtrabanco Bundle

Read-only workflow sensor: compute repository, roadmap, dependency, PR, finding, and recovery state, then emit the fixed machine envelope. Never edits. Triggers: "workflow-status", "workflow status", "what can I build next", "state of the run".

gtrabanco Bundle

Internal step of plan-feature: from an already-designed SPEC (product half `designed`), fill the **engineering half** and generate the planning artifact set scaled to the feature's size (XS/S → SPEC-only with ≥ 2 phases in the SPEC, last = Hardening & PR; M/L → full set with a hardening phase), freeze one compact ACCEPTANCE.md for every size, and register the roadmap entry. Docs only — never code.

gtrabanco Skill

Internal step of plan-feature: turn a feature-request issue into a scoped, sized, roadmap-mapped SPEC **product half** (capability closure satisfied) with Closes #N traceability.

gtrabanco Skill

Internal contract: the single owner of the bounded pre-write implementation discovery step. One read-only mapper that closes seven evidence questions, emits one fixed compact map, and routes READY | REPLAN | NEEDS-DESIGN | BLOCKED before any branch, planning, or source write. Consumed only by execute-phase on the pre-write route. Not a menu entry.

parcadei Skill

Interactive workspace discovery - learn what tools, workflows, agents, and hooks are available

iamk77 Bundle

The open-source discovery lens: find the few repositories worth your time — before you sink hours into the wrong one — in either mode finding happens in: TARGETED (a concrete need — the agent fans out every search seam in parallel and returns a ranked, deduped shortlist) or SERENDIPITOUS (no goal — the agent ranges the high-signal surfaces and brings back orthogonal finds, captured cheaply). The one shift: search-syntax mastery is COMMODITIZED, so your edge is the NEED-SPEC and which seams to mine, and serendipity is HARVESTED, not searched. Use when looking for a library, tool, framework, reference implementation, or alternative; when browsing for interesting projects; or when you keep hitting the same dead high-star repos. Triggers on "find a library/tool for X", "alternative to Y", "what should I use for", "is there a repo that", "show me interesting projects", "good first issue", "discover repos", "browse GitHub", "find open-source projects". Hands its shortlist to `touchstone` for evaluation.

morningstar0709 Bundle

Run an agency-orchestrator style YAML workflow inside the current Trae conversation by simulating or coordinating multiple roles. Use when the user provides a `.yaml` or `.yml` workflow, asks for multi-role collaboration, says things like “用多个角色一起评审这个 PRD”“多角色协作”“先生成工作流再执行”“让产品经理、架构师、QA 一起看一下”, or wants roles such as product manager, architect, reviewer, or QA to work together. Supports layered execution, role prompting, variable interpolation, document-backed inputs, and parallel steps only when the current environment has a clear subagent mapping. Do not use for ordinary implementation plans, simple code changes, or tasks already covered by `writing-plans`, `executing-plans`, `subagent-driven-development`, or single-purpose review/debug skills.