hpsgd/turtlestack - Page 6

compliance-audit

Audit compliance against a regulatory framework — gap analysis, evidence collection, and remediation planning.

risk-assessment

Conduct a risk assessment — identify, analyse, and evaluate risks with quantified likelihood, impact, and treatment plans.

review-git

Review git conventions — commit messages, PR titles, branch model, and content date integrity. Auto-invoked during PR and commit workflows.

review-typescript

Review TypeScript and Next.js code against team conventions — type safety, component patterns, API routes, testing, and bundle hygiene. Auto-invoked when reviewing .ts/.tsx files.

create-skill

Create a new skill following the standard template. Handles SKILL.md creation, README update, and parent agent cross-reference.

algorithm

Structured seven-phase execution methodology for complex tasks. Transition from current state to ideal state using verifiable criteria. Use for any non-trivial work that benefits from systematic execution.

council

Simulate a structured debate between diverse expert perspectives. Use when weighing options, making decisions, or needing multiple viewpoints on a problem.

creative

Divergent ideation and creative brainstorming. Use when you need novel solutions, want to break out of conventional thinking, or need multiple distinct approaches.

first-principles

Deconstruct a problem to fundamental truths and rebuild from scratch. Use when stuck, challenging inherited constraints, or making architecture decisions where convention may be wrong.

iterative-depth

Analyse a problem through multiple structured passes from different lenses. Use for requirements analysis, architecture decisions, or any problem that benefits from multi-angle examination.

learning

Capture, categorise, and recall learnings from work sessions. Use after completing work, when something unexpected happens, or when explicitly asked to remember something.

red-team

Adversarial analysis to stress-test an idea, plan, or argument. Use to find every weakness before they find you. Purely adversarial — for balanced debate, use /council instead.

scientific-method

Apply the scientific method to any problem — define goal, hypothesise, experiment, measure, iterate. The meta-skill governing all structured investigation. Use when debugging, validating assumptions, or turning uncertainty into knowledge.

wisdom

Build and query domain-specific wisdom frames — crystallised patterns from accumulated experience. Use to capture high-confidence principles or to consult accumulated wisdom before making decisions.

churn-analysis

Analyse churn risk for a customer or segment — diagnose root cause, design intervention, and define success criteria for retention.

write-qbr

Prepare a Quarterly Business Review for a customer account. Produces a structured QBR document with value delivered, usage highlights, and strategic recommendations. Use before quarterly customer meetings.

write-sdk-guide

Write an SDK or client library guide — installation, quick start, configuration, common patterns, and error handling. Produces a complete developer reference from zero to production usage.

write-architecture-doc

Write or update architecture documentation — system overview, component diagrams, data flows, bounded contexts, and key decisions. Produces a living document that explains boundaries and why, not implementation details.

write-user-story

Write user stories with Gherkin acceptance criteria, edge cases, anti-requirements, and ISC-validated criteria from a feature description or PRD section.

feedback-synthesis

Synthesise customer feedback into themes — aggregate issues, feature requests, and praise from support tickets, reviews, or survey responses.

triage-tickets

Triage support tickets or issues — categorise, assign severity, identify routing, and flag patterns.

write-user-guide

Write a task-oriented user guide for a feature or workflow. Written in product language for non-technical readers. Produces step-by-step instructions with expected results and troubleshooting.

journey-map

Map a customer journey — stages, touchpoints, actions, emotions, pain points, and opportunities. Produces a structured journey map with critical moments and prioritised recommendations. Use for understanding end-to-end user experience or identifying friction…

persona-definition

Define a research-backed user persona grounded in real behaviour, not demographics or stereotypes. Produces a structured persona with goals, frustrations, and behaviour patterns backed by evidence. Use to represent a customer segment for product and design…

usability-review

Review a product, feature, or flow for usability issues using Nielsen's 10 heuristics. Produces a prioritised findings table with severity ratings and specific fix recommendations. Use for experience audits, friction identification, or pre-launch UX review.

usability-test-plan

Plan a usability test — define research questions, tasks, participant criteria, and analysis approach. Produces a structured test plan ready for execution. Use before conducting moderated or unmoderated usability testing with real users.

write-changelog

Generate a changelog from git history, PRs, or a list of changes. Written for the target audience (users or developers).

write-kb-article

Write a knowledge base article from a resolved support issue, common question, or how-to topic.