Product & Planning

weakened-fixedinvestmenttrust229 Skill

제품 디스커버리 구조화를 위한 Opportunity Solution Tree(OST)를 구축합니다 — 원하는 결과를 기회, 솔루션, 실험으로 연결합니다. Teresa Torres의 Continuous Discovery Habits 기반. 디스커버리 작업 구조화, 기회와 솔루션 매핑, 다음 빌드 결정 시 활용하세요.

weakened-fixedinvestmenttrust229 Skill

신규 제품을 위한 린 스타트업 실험(프리토타입)을 설계합니다. XYZ 가설을 수립하고 랜딩 페이지, 설명 영상, 사전 주문 같은 저비용 검증 방법을 제안합니다. 신규 제품 아이디어 검증, 프리토타입 제작, 또는 시장 수요 테스트 시 사용합니다.

weakened-fixedinvestmenttrust229 Skill

기존 제품의 기능 아이디어에 대한 가치, 사용성, 실행 가능성, 기술 타당성 측면의 위험 가정을 식별합니다. 다각적 악마의 변호인 사고를 활용합니다. 기능 아이디어 검증, 위험 평가, 또는 가정 매핑 준비 시 사용합니다.

weakened-fixedinvestmenttrust229 Skill

기존 제품의 가정을 검증하기 위한 실험을 설계합니다 — 프로토타입, A/B 테스트, 스파이크, 기타 저비용 검증 방법. 가정 검증, 기능 아이디어를 저렴하게 테스트, 또는 제품 실험 계획 시 사용합니다.

lauraflorentin Bundle

User research, persona development, jobs-to-be-done mapping, and opportunity scoring for startup and enterprise PMs — guerrilla interviews, formal research plans, proto-personas, data-backed segmentation, JTBD frameworks, and Opportunity Solution Trees. Use when user asks to "run product discovery", "user research plan", "build personas", or mentions customer interviews, jobs-to-be-done, or opportunity scoring.

lauraflorentin Bundle

Project charters, stakeholder mapping, and kickoff planning for software and general PMs Use when user asks to "create a project charter", "map stakeholders", "kick off a project", or mentions project setup, stakeholder analysis, or kickoff meeting.

lauraflorentin Bundle

Design, conduct, and synthesize stakeholder interviews for consulting engagements — question design, interview protocols, note-taking, cross-interview synthesis, and insight generation. Use whenever stakeholder interviews, interview guides, question banks, interview synthesis, qualitative research, or discovery interviews come up. Use when user asks to "create interview guides", "stakeholder interview plan", "discussion guide", or mentions research interviews, structured interviews, or interview questions.

lauraflorentin Bundle

Organizational change management (OCM) for consulting engagements — stakeholder mapping, impact assessment, communication planning, training design, adoption tracking, and resistance management. Use this skill whenever change management, OCM, stakeholder mapping, adoption, resistance, communication plans, training rollouts, or organizational readiness come up. Use when user asks to "plan change management", "change readiness assessment", "stakeholder adoption plan", or mentions organizational change, resistance management, or transition planning.

lauraflorentin Bundle

Quick-access analytical thinking frameworks for management consultants — from root cause analysis and phased implementation to stakeholder accountability and rapid executive communication. Designed for in-the-moment problem solving during client engagements. Use when user asks to "apply a framework", "MECE analysis", "hypothesis-driven", or mentions issue trees, pyramid principle, or structured problem-solving.

nolte Bundle

Runs the audience-identification methodology from spec/project/audience-identification/ against a bounded context (software module, service, library, or whole project) and produces an authoritative audience artifact. Invoke when the user says things like "identify audiences for this module", "who are the consumers/users of X", "stakeholder identification for X", "audience analysis before I write the README / SLA / threat model", "list the audiences of this library", or equivalent German-language requests. Also triggers when another spec or skill (readme-structure, future SLA or threat-modeling specs) needs to reference an audience list that does not yet exist for the current context. Don't use to review an existing audience artifact for compliance (use audience-review). Supports resume on re-invocation per `spec/claude/resumable-work/`.

nolte Bundle

Orchestrates a raw GitHub issue to an open, audit-trailed pull request per `spec/project/issue-orchestration/`. Comprehends the issue (body, comments, labels, linked items, repo surface), classifies it (`bug / feature-request / spec-change / security / docs / refactor / question / infra`), decomposes it into atomic specialist-ready work packages persisted as a pre-analysis artifact, routes large issues into the formal roadmap→feature→sprint pipeline, dispatches each package to the most specialised available skill or agent resolved by runtime lookup, and verifies via `quality-gate` and the standard PR flow. Invoke when the user asks to "analyse this issue", "orchestrate issue #N", "take this issue end-to-end", or equivalent German requests. Don't use to merge the PR (use `pull-request-merge`), to triage a red CI run (use `workflow-health-triage`), or to decompose an existing roadmap item (use `feature-decompose`). Supports resume per `spec/claude/resumable-work/`.

nolte Bundle

Captures or refreshes the `tech_stack:` block in a Portfolio-Member's `project/portfolio.yml` per the canonical-language file under `spec/portfolio/tech-stack-discovery/` §Discovery sequence. Probes repo signals (lockfiles, `Taskfile.yml`, `.github/workflows/`, `renovate.json5`, `mkdocs.yml`, `.vale.ini`, `.pre-commit-config.yaml`), classifies hits against the closed `kind` (12) and `group` (5) enums from `spec/portfolio/tech-stack/`, compares each candidate against the global stack, drops inherited matches, and confirms every proposed change interactively before writing. Invoke when the user asks to "capture the tech stack", "scaffold a tech_stack block", "refresh the tech_stack section", or equivalent German-language requests. Don't use to author `portfolio/tech-stack.yml` (hand-curated only) or to run signal-verification audits (use `portfolio-audit`). Supports resume on re-invocation per `spec/claude/resumable-work/`.

nolte Bundle

Runs the requirements-elicitation interview methodology from spec/project/requirements-elicitation/ to capture a user's requirements precisely, assuming the user often does not know exactly what they want, expresses it imperfectly, or is misread. Drives a one-question-at-a-time funnel interview, maintains a per-dimension confidence score plus a gap matrix, asks confidence-gated clarifying questions only where understanding is weak, and writes an authoritative artifact to project/requirements/<slug>.md. Invoke when the user says things like "elicit the requirements for X" or "I want to build something but I'm not sure what exactly", or equivalent German-language requests. Also triggers as the upstream gate of roadmap-plan, feature-decompose, and issue-orchestrate when a requirement artifact is missing or below threshold. Don't use to decompose an existing requirement set (use feature-decompose) or author the downstream spec (use spec). Supports resume per `spec/claude/resumable-work/`.

nolte Bundle

Creates a new sprint file under project/sprints/ per the project sprint spec. Invoke when the user asks to plan a sprint, open a sprint, draft the next sprint, schedule a sprint, or pull roadmap items into a sprint. Also handles equivalent German-language requests. Resolves the next monotonic sprint number, walks the value-delivery contract (rejects operator-internal verbs in `value_statement`), pulls in roadmap items whose `target_sprint` matches, populates the `features` list (delegating to `feature-decompose` when decompositions are missing), names the value-verifying feature, and writes the file with `status: planned`. Supports resume on re-invocation per `spec/claude/resumable-work/`.

nolte Bundle

Scaffolds the project planning pair `project/goals.md` and `project/roadmap.md` for the first time, per `spec/project/roadmap/`. Invoke when the user asks to "set up the roadmap", "initialise project goals", "create goals.md and roadmap.md", "bootstrap the roadmap", or any equivalent fresh-bootstrap request. Also handles equivalent German-language requests. Verifies the audience artefact exists (and dispatches `audience-identify` when it doesn't), drafts the Vision plus numbered Outcomes in `project/goals.md`, drafts an empty queue plus optional phase headings in `project/roadmap.md`, presents both files for explicit approval, then writes them. Do NOT use to add roadmap items, retarget sprints, or flip MVP flags — that is `roadmap-plan`. Do NOT use to enforce the detail-level invariant — that is `roadmap-refine`. Supports resume on re-invocation per `spec/claude/resumable-work/`.

nolte Bundle

Adds, retargets, and reshapes roadmap items in `project/roadmap.md` per `spec/project/roadmap/` and `spec/project/mission/`. Invoke when the user asks to "add a roadmap item", "queue work for sprint N", "promote roadmap item to fine", "retarget R-3 to sprint 9", "flip MVP on this item", or equivalent German-language requests. Validates outcome IDs against `goals.md`, validates `target_sprint` against `project/sprints/`, enforces the lifecycle transitions declared in the roadmap and mission specs (including the asymmetric MVP-flag rule: `false→true` allowed before stabilisation, `true→false` forbidden after the item entered `status: active`), and refuses partial writes that would leave inconsistencies. Don't use to scaffold the roadmap from scratch (use `roadmap-init`) or to enforce the detail-level invariant (use `roadmap-refine`). Supports resume on re-invocation per `spec/claude/resumable-work/`.

nolte Bundle

Revises an existing `project/mission.md` per the canonical-language file under spec/project/mission/. Invoke when the user says "revise the mission", "update project/mission.md", "flip mvp_status", "the MVP is achieved", "the stabilisation gate is satisfied", or equivalent German-language requests. Supports three operations: (1) revise statement, audiences, verifying-feature pointer, or time_bound; (2) flip `mvp_status` along the legal lifecycle (`defining→in_progress→achieved→stabilised`, plus regression path); (3) revise after stabilisation with the mandatory rationale. Verifies the stabilisation-gate conditions by reading `project/roadmap.md` and `project/sprints/` before allowing a flip to `stabilised`. Supports resume on re-invocation per `spec/claude/resumable-work/`.

nolte Bundle

Enforces the detail-level invariant on `project/roadmap.md` per `spec/project/roadmap/` §Detail-level convention. Invoke when the user asks to "refine the roadmap", "check roadmap detail levels", "is the roadmap ready for the next sprint", "promote roadmap items to fine", or equivalent German-language requests. Resolves the current and next sprint by reading `project/sprints/`, walks every roadmap item, emits a structured violation record on stderr for every item with `target_sprint` equal to the current or next sprint and `detail` other than `fine`, exits non-zero when any violation is open, and walks per-item fix proposals one at a time. Don't use to add items, retarget sprints, or flip MVP flags (use `roadmap-plan`); don't use to scaffold the roadmap from scratch (use `roadmap-init`). Supports resume on re-invocation per `spec/claude/resumable-work/`.

nolte Bundle

Decomposes a roadmap item into feature files under project/features/ per spec/project/feature/. Invoke when the user asks to decompose a roadmap item, break down a roadmap entry into features, draft features, scaffold a feature file, plan features for the next sprint, or write a new feature. Also handles equivalent German-language requests. Walks the operator through title, description, 3-7 testable acceptance criteria, and test hooks per feature; identifies which carries `verifies_sprint_value`; dispatches `feature-consistency-reviewer` (or records a manual fallback) before allowing the feature to leave `draft`. Don't use to transition feature status (`ready → in_progress` / `in_progress → done` is `sprint-execute` / `sprint-review`) or to author roadmap items, sprints, or the mission file. Supports resume on re-invocation per `spec/claude/resumable-work/`.

heyzgj Skill

<design-system>

heyzgj Skill

Dark, atmospheric nightlife discovery platform inspired by Resident Advisor and Criterion Channel. Event feed rows with genre-coded pills, artist spotlights, venue cards with moody photography, editorial magazine section, and typographic city selector. Violet-tinted OKLCH dark palette (hue 290) with warm amber accent (hue 65). Syne display + Instrument Sans body. Data-dense event rows are the primary visual -- lineups, times, venues, prices, and ticket status.

pekral Skill

Use when a PRD or product intent is clear but the implementation constraints are not — turns a vague capability ask into an engineering-ready plan that exposes invariants, interfaces, and unresolved decisions before any code is written.

hvkshetry Skill

Build a 12-24 month value creation roadmap for private holdings with measurable KPI targets.

shipshitdev Skill

Use when the user wants to draft, scope, or formalize a feature for shipcode — "write a PRD for X", "let's plan X", "scope this out", "what should X do", or when a GitHub issue body needs to be fleshed out before the pipeline plans it. Writes a PRD that maps cleanly onto shipcode's pipeline (objective / acceptanceCriteria / outOfScope / estimatedComplexity) so the planner agent can consume it without re-elicitation. Do NOT use for code edits, debugging, or PR reviews.

shipshitdev Bundle

Create a well-written PRD, task, or GitHub issue/sub-issue for a feature, bug, or enhancement. Use when planning work, writing GitHub issues, breaking down epics into sub-issues, or creating local task files. Common prompts: create a task, write a PRD, open a GitHub issue, create a sub-issue, plan this feature, write up this bug, break this down into issues, I want to add X, implement Y.

cogine-ai Bundle

Summarize and review a sales call from notes or a transcript, extract commitments and risks, draft the customer follow-up, and optionally coach the seller. Use after discovery, demo, negotiation, executive, or closing calls; when logging a call; when a manager or rep wants evidence-based feedback; or when the next step is unclear.

cogine-ai Bundle

Build and qualify sourced prospect lists for B2B SaaS, general B2B, local businesses, or early demand-signal discovery. Use when finding leads, ICP-fit accounts, first customers, design partners, beta users, or public evidence of a problem. Use cold-email after the list is ready and account-research for a deep single-account brief.

cogine-ai Bundle

Explicitly synthesize the current conversation into a PRD or spec and publish it to the configured tracker.

cogine-ai Bundle

Write a concise, measurable product requirements document for a new product, feature, or AI capability. Use when a validated product direction needs a shared contract for users, scope, outcomes, requirements, rollout, and risks.

cogine-ai Bundle

Help users build a robust enterprise sales engine by mastering founder-led discovery, navigating complex procurement cycles, and designing products that meet organizational governance needs.

cogine-ai Bundle

Create, update, or reprioritize a product roadmap with explicit tradeoffs, dependencies, risks, and change history. Use when priorities, scope, status, or timing must change after new information.

cogine-ai Bundle

Choose content pillars, topics, formats, distribution, editorial cadence, and a measurable content roadmap. Use when deciding what to create and why; use copywriting for individual pages and search-visibility for search discovery.

cogine-ai Bundle

Audit and improve qualified discovery across traditional and AI search. Use for SEO or indexing problems, ranking declines, AI citations and recommendations, GEO/AEO, content discoverability, or scalable programmatic-search opportunities.

cogine-ai Bundle

Build and maintain an evidence-based plan for a complex enterprise account using stakeholder mapping, MEDDPICC, deal-health checks, stage gates, and a mutual action plan. Use for strategic accounts, multi-stakeholder deals, economic-buyer access, procurement or security paths, stalled opportunities, proposal readiness, or deciding the next actions for one major deal.

cogine-ai Bundle

Turn ambiguous product or bug requests into de-duplicated, implementation-ready specs with acceptance criteria and validation.

cogine-ai Bundle

Synthesize interviews, surveys, support feedback, usability notes, and product data into evidence-backed findings, opportunity areas, and recommendations. Use when raw research must inform a product decision or roadmap.