TSH Product Management

Plugin tsh-product-management from marketplace tsh-agentic-collections in TheSoftwareHouse/agentic-collections. Commands read from the repo's manifest — today.

Skills (16)

• adding-project-context-workspace

  Creates a new workspace in a project's `<project>-context` knowledge base — the folder, its README index, its CLAUDE.md with exactly one named owner, and its row in the area map, all in one change. Use when a new layer or area of such a project needs its own place: a new delivery layer, a workstream

• analyze-materials

  Entry point for the full business-analysis workflow: processes discovery workshop materials into Jira-ready epics and user stories, or imports an existing Jira backlog to iterate on. Run /tsh-product-management:analyze-materials with a transcript path, Figma link, PDF path, folder, Jira issue keys,

• analyzing-discovery-context

  Gathers and expands the business context around a task or workshop topic: pulls what is known from task trackers, knowledge bases, documents and designs, finds the gaps, resolves them with the user, and writes a research report. Use before committing to a backlog, when a request is ambiguous, or whe

• domain-dictionary

  Entry point for producing, reviewing and maintaining a per-product domain dictionary — the canonical business-term glossary, not domain-driven design. Run /tsh-product-management:domain-dictionary with a project name, a workshop directory of transcripts, PDFs or designs, a repository path to reconci

• explore-materials

  Entry point for Explore Mode: reads discovery workshop materials and produces a business-context summary with likely epic candidates and open questions, without creating any backlog items. Run /tsh-product-management:explore-materials with a transcript path, Figma link, PDF path, or folder of worksh

• extracting-epics-and-stories

  Turns processed workshop materials into a business-oriented backlog: an approved intent brief first, then epics as independently demonstrable vertical slices with a delivery contract, and user stories with source traceability and GIVEN/WHEN/THEN acceptance criteria. Use after transcripts and materia

• formatting-jira-issues

  Transforms an approved epic and story list into Jira-ready issues against a benchmark template — field mapping, Jira markdown, completeness validation, the formatting review and the Gate 2 push approval — and imports an existing Jira backlog into the same local format for iteration. Use before creat

• initializing-project-context

  Sets up a project's context repository — a knowledge base with named owners per project and delivery layer, one folder for all decision records, a quality gate, and a Claude Code marketplace for the project's own Markdown skills — as a local git repository it can publish to Bitbucket, GitHub or any

• managing-domain-dictionaries

  Produces, reviews and maintains a per-product domain dictionary — canonical business terms, their source-language surface forms, and where a UI label differs from the identifier — through Harvest, Reconcile and Interview modes, checked by eleven review passes and reconciled against a live codebase w

• navigating-project-context

  Reads a project's knowledge base — the `<project>-context` repository: scope, accepted decisions, vocabulary, who owns what — before work that depends on it, wherever the clone sits, and cites the file, its last change and its owner behind every project fact. Use when a task in a repository of such

• orchestrating-business-analysis

  Runs the business-analysis workflow end to end from the main conversation: turns discovery workshop material — transcripts, Figma, PDFs, codebase context — into Jira-ready epics and user stories and a delivery roadmap, behind five human review gates, delegating the heavy reading to read-only worker

• planning-delivery-roadmaps

  Reconciles approved epics, accepted quality findings, a project baseline and any existing roadmap into one Markdown-only, per-project roadmap: client-facing outcome waves and an internal coordination view, linked by project-scoped stable epic IDs. Use after the task list is confirmed and before Jira

• processing-workshop-transcripts

  Cleans a raw workshop or meeting transcript into a structured, business-relevant document — small talk and filler removed, content grouped by discussion topic, with decisions, action items and open questions extracted. Use before any backlog extraction when the input is a raw transcript, meeting not

• repairing-project-context-links

  Finds and repairs broken references in a project's `<project>-context` knowledge base — relative links that no longer resolve, filenames that are not kebab-case, and markdown tables that render wrongly — using the repository's own checker scripts. Use when those scripts report violations, before ope

• reviewing-backlog-quality

  Systematically reviews an approved epic and story list for gaps, missing edge cases and delivery-readiness problems, then produces individually accept-or-reject suggestions that refine the backlog before Jira formatting. Runs Lite or Full analysis passes over a domain model built from the tasks them

• writing-project-knowledge

  Adds or updates a document in a project's knowledge base — the `<project>-context` repository — picking the owning workspace, applying the state-of-today rule, updating the workspace index, and naming the owner who reviews it. Use when something learned or changed on such a project should be written

Subagents (7)

• backlog-extractor

  Drafts intent briefs and extracts epics and user stories from approved workshop context — with delivery contracts, source traceability and GIVEN/WHEN/THEN acceptance criteria — and returns them as a report. Use one agent per epic to extract a large backlog in parallel.

• backlog-quality-reviewer

  Runs assigned Lite or Full quality-review passes over an approved epic and story list and returns structured, confidence-scored suggestions — lifecycle gaps, missing edge cases, delivery-readiness problems. Use to split a review across several agents, one batch of passes each, before the Gate 1.5 di

• discovery-analyst

  Synthesizes workshop materials — transcripts, PDFs, supplied design and backlog context — into a structured business summary with likely epic candidates, baseline overlap, contradictions and open questions. Use for Explore Mode and for the material-analysis phase before extraction, including one age

• jira-formatter

  Applies the Jira benchmark template to extracted epics and stories, produces the completeness table, and prepares post-push verification diffs and baseline-refresh content. Use to keep bulk formatting work out of the main conversation; it performs no Jira calls and writes no files.

• roadmap-planner

  Reconciles approved epics, accepted quality findings, a project baseline and any existing roadmap into one validated, in-memory roadmap proposal — stable epic IDs, client-facing outcome waves and an internal coordination view. Use as a single agent before the Roadmap Review gate; never split the wor

• terminology-extractor

  Extracts domain-term candidates and source-language surface forms from supplied material, and sweeps a codebase's identifiers for Reconcile mode. Use for the harvest reading pass of managing-domain-dictionaries and for the identifier sweep that reconciling-with-code diffs against the term table.

• transcript-cleaner

  Cleans and structures a raw workshop or meeting transcript — removing small talk and filler, grouping by discussion topic, extracting decisions, action items and open questions — and returns it as a report. Use to process transcript material without spending the main conversation's context on the ra

Hooks (5)

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

• PreToolUse

  node

Similar plugins