By hpsgd
Product owner — requirements, user stories, acceptance criteria, backlog prioritisation
Bootstrap the product documentation structure for a project. Creates docs/product/, generates initial templates, and writes domain CLAUDE.md. Idempotent — merges missing sections into existing files without overwriting.
Review and groom a backlog — classify items by readiness, break large items into deliverables, add acceptance criteria, RICE-score, and recommend actions.
Define a Jobs-to-be-Done analysis for a product or feature area. Produces structured job statements, outcome expectations, and hiring/firing criteria. Use when entering a new problem space, validating product-market fit, or reframing features as customer jobs.
Write a Product Requirements Document from rough notes or a feature idea. Produces a structured PRD with problem validation, user definition, RICE prioritisation, acceptance criteria, and scope.
Create a user story map — a spatial arrangement of stories along a narrative backbone. Produces a backbone of user activities, a walking skeleton, and release slices. Use when planning a new feature area, epic, or release to ensure coverage and sequence.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A plugin marketplace for Claude Code. Agents, skills, rules, and conventions that work together as a virtual team.
/plugin marketplace add hpsgd/turtlestack
Start with the core plugins (rules, thinking skills, and code review), then add agents for your stack:
/plugin install coding-standards@hpsgd
/plugin install writing-style@hpsgd
/plugin install security-compliance@hpsgd
/plugin install thinking@hpsgd
/plugin install tooling@hpsgd
/plugin install code-reviewer@hpsgd
/plugin install ai-engineer@hpsgd
Add a technology stack if relevant:
/plugin install dotnet-stack@hpsgd
/plugin install nextjs-stack@hpsgd
/plugin install python-stack@hpsgd
Then reload:
/reload-plugins
Browse the full plugin list below to see what else is available.
Per-project overrides. Create your own .claude/rules/ files. Project-level rules take precedence over marketplace rules.
Disabling a plugin. Set it to false in .claude/settings.json:
{
"enabledPlugins": {
"writing-style@hpsgd": false
}
}
Local overrides (not committed). Use .claude/settings.local.json for personal preferences that shouldn't affect the team.
{
"enabledPlugins": {
"coding-standards@hpsgd": true,
"writing-style@hpsgd": true,
"security-compliance@hpsgd": true,
"thinking@hpsgd": true,
"tooling@hpsgd": true,
"code-reviewer@hpsgd": true,
"dotnet-stack@hpsgd": true,
"nextjs-stack@hpsgd": true,
"python-stack@hpsgd": true,
"plugin-curator@hpsgd": true,
"coordinator@hpsgd": true,
"cpo@hpsgd": true,
"product-owner@hpsgd": true,
"ui-designer@hpsgd": true,
"ux-researcher@hpsgd": true,
"user-docs-writer@hpsgd": true,
"developer-docs-writer@hpsgd": true,
"internal-docs-writer@hpsgd": true,
"gtm@hpsgd": true,
"support@hpsgd": true,
"customer-success@hpsgd": true,
"grc-lead@hpsgd": true,
"cto@hpsgd": true,
"architect@hpsgd": true,
"react-developer@hpsgd": true,
"dotnet-developer@hpsgd": true,
"python-developer@hpsgd": true,
"ai-engineer@hpsgd": true,
"qa-lead@hpsgd": true,
"qa-engineer@hpsgd": true,
"release-manager@hpsgd": true,
"performance-engineer@hpsgd": true,
"devops@hpsgd": true,
"security-engineer@hpsgd": true,
"data-engineer@hpsgd": true,
"analyst@hpsgd": true,
"investigator@hpsgd": true,
"workflow-tools@hpsgd": true
}
}
After installing plugins, scaffold your project with domain-specific docs:
/coordinator:bootstrap-project my-project
npx claudepluginhub hpsgd/turtlestack --plugin product-ownerInternal documentation writer — architecture docs, runbooks, changelogs, onboarding guides, ADR documentation. Writes for engineers who know the domain but may be new to the codebase.
Go-to-market specialist — positioning, launch strategy, content marketing, competitive analysis
Customer support — ticket triage, feedback synthesis, knowledge base, bug escalation
Security baseline rules and audit skills for maintaining secure code
Developer documentation writer — API references, SDK guides, integration tutorials, code examples. Writes for developers who are competent but unfamiliar with your codebase.
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
PRDs, user stories, acceptance criteria, and technical specifications.
Product management: ticket-info, user-stories-create, prd, spec
Agent-first PM toolkit with 9 specialist agents and 18 skills for solo developers and small teams
Pipeline PRD/GSD → JTBDs → User Stories validadas y priorizadas. 7 skills + 11 comandos. Source-agnostic (acepta PRD pegado, fichero o URL — sin acoplamiento a Notion/Jira). Incluye `/from-gsd` para integrar artefactos de Get Shit Done y `bridge/gsd-bridge.py` para mantener consistencia entre planning y ejecución.
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.