Product & Planning

ai-driven-dev Bundle

Clarify a vague product or technical intent through natural discovery. Use when the user has a half-formed idea, ambiguous request, or asks to brainstorm, discover, refine, or clarify. Not for artifact gap scans, planning, or code.

ai-driven-dev Bundle

Scan a markdown artifact (idea, stories, PRD, spec) for blind spots into a shadow report grouped by category and severity. Use to find gaps or what is missing in a written artifact. Not for interactive Q&A or code review.

ai-driven-dev Bundle

Orchestrates a product backlog end to end. Use when the user wants to ask what it holds, or to run intake, triage, refinement, review, lifecycle events, ordering, health checks, or repair. Not for one known artifact step.

ai-driven-dev Bundle

Generate a Product Requirements Document from a feature description or user stories.

ai-driven-dev Bundle

Help users discover installed skills and find the right one for their use case.

stacksjs Skill

Use when performing WHOIS lookups in Stacks — domain queries, batch lookups, SOCKS proxy support, TLD server discovery, response parsing, the WhoIsParser class, or the built-in SocksClient. Covers @stacksjs/whois.

stacksjs Skill

Use when implementing real-time features in Stacks — WebSocket broadcasting, public/private/presence channels, emit to users, the Channel class, broadcast discovery, server lifecycle, or realtime configuration. Covers @stacksjs/realtime and config/realtime.ts.

stacksjs Skill

Use when working with the Stacks extension registry — framework extension metadata, package discovery, or the registry system. Covers @stacksjs/registry.

jovanipink Skill

Build a proposed domain vocabulary from current code, documents, and stakeholder language, including concepts, definitions, relationships, invariants, authorities, examples, and contradictions. Use when inconsistent terms are causing design or communication errors; do not treat the result as ratified without owner evidence.

jovanipink Bundle

Apply focused Go engineering judgment after repository gate discovery. Use for Go modules, packages, concurrency, APIs, tests, dependencies, compatibility, and build concerns; defer exact commands to repository evidence.

jovanipink Bundle

Apply focused Python engineering judgment after repository gate discovery. Use for Python packages, typing, async behavior, tests, dependencies, compatibility, and builds; defer exact commands to repository evidence.

jovanipink Bundle

Apply focused Adobe Experience Manager engineering judgment after repository gate discovery. Use for AEM as a Cloud Service or AEM 6.5 code, Sling and OSGi, content packages, Dispatcher, caching, tests, compatibility, and builds; preserve separate Cloud Manager authority.

jovanipink Bundle

Apply focused Terraform engineering judgment after repository gate discovery. Use for modules, providers, state, plans, upgrades, compatibility, and infrastructure review; validation never implies apply authority.

jovanipink Bundle

Apply focused PHP and Drupal engineering judgment after repository gate discovery. Use for Composer projects, Drupal modules or themes, entity and configuration APIs, caching, security, tests, compatibility, and builds; defer exact commands to repository evidence.

jovanipink Bundle

Review or design a Google Agent Development Kit system using exact framework, language, model, session, tool, evaluation, and deployment evidence. Use for human-facing ADK architecture and version discovery; combine it with the focused agent security, evaluation, context, retrieval, and operational skills instead of treating framework defaults as proof of safety or readiness.

jovanipink Bundle

Translate technical evidence for a named stakeholder decision without overstating certainty, hiding risk, or exposing inappropriate detail. Use for executive summaries, review packets, status updates, decision briefs, and cross-functional explanations.

jovanipink Bundle

Apply focused Java and Spring engineering judgment after repository gate discovery. Use for JVM services, Spring Boot applications, concurrency, transactions, tests, dependencies, compatibility, and builds; honor repository wrappers and toolchains.

jovanipink Bundle

Apply focused C# and .NET engineering judgment after repository gate discovery. Use for .NET applications, libraries, ASP.NET Core, Entity Framework Core, async behavior, tests, packages, compatibility, and builds; defer exact commands to repository evidence.

jovanipink Bundle

Apply focused Swift and SwiftUI engineering judgment after repository gate discovery. Use for packages, applications, concurrency, UI state, tests, compatibility, and builds; require observed macOS evidence for Apple toolchain claims.

jovanipink Bundle

Apply focused PostgreSQL and SQL engineering judgment after repository gate discovery. Use for schemas, queries, transactions, migrations, indexing, compatibility, and database test concerns; never mutate shared data merely to validate.

jovanipink Bundle

Apply focused Salesforce, Apex, and Lightning Web Components engineering judgment after repository gate discovery. Use for metadata projects, packages, governor limits, data access, tests, compatibility, and deployment readiness; preserve separate live-org authority.

jovanipink Bundle

Review interoperability across agent, tool, and service protocols using exact versions, discovery records, schemas, identity, authorization, delegation, streaming, errors, retries, idempotency, cancellation, and trust zones. Use for A2A, MCP, or another agent-facing protocol boundary; use api-contract-compatibility-review for an ordinary API change without agent delegation semantics.

jovanipink Bundle

Apply focused TypeScript and JavaScript engineering judgment after repository gate discovery. Use for Node or browser packages, type safety, async behavior, tests, dependencies, compatibility, and builds; honor the repository package manager and scripts.

mrciphersmith Bundle

Use when PRD and BRD exist and need to be expanded into a Functional Specification Document (FSD) detailing feature behavior, UI states, logic rules, and interface contracts.

mrciphersmith Bundle

Use when PRD and FSD exist and need to be expanded into a Technical Requirements Document (TRD) covering architecture, tech stack, data models, API contracts, and non-functional requirements.

mrciphersmith Bundle

Generates roadmap, milestones, task breakdown, and dependency graph from PRD. Use when: dispatched by gproject-orchestrator Phase 6. NOT for: direct user invocation.

mrciphersmith Skill

Use when a user request needs to be converted into a full pre-implementation documentation suite (BRD → PRD → FSD → TRD) with iterative review at each document stage.

mrciphersmith Bundle

Collects and structures initial project information from multiple sources. Use when: dispatched by gproject-orchestrator Phase 0. NOT for: direct user invocation — always called through orchestrator.

mrciphersmith Bundle

Use when a vague or unstructured request needs to be converted into a formal, testable Product Requirements Document.

mrciphersmith Bundle

Generates PRD or Implementation Plan constrained by decisions registry, architecture doc, and best practices. Does NOT invent new architectural decisions. Use when: dispatched by gproject-orchestrator Phase 4. NOT for: direct user invocation.

mrciphersmith Bundle

Project documentation orchestrator — builds PRDs, specs, and implementation plans through a phased pipeline of specialized subagents. Use when: "Create project documentation", "Write PRD for...", "Plan project...", "Document how to implement...", "Spec out feature...", "Project planning", "gproject", "Создай документацию проекта", "Напиши PRD". Make sure to use this skill whenever the user mentions PRD, project planning, technical specification, implementation plan, feature spec, architecture document, project documentation, or wants to plan any software project from scratch or document a new feature in an existing codebase — even if they don't explicitly say "PRD" or "spec". Also trigger on: "how should I build...", "plan out...", "what's the best approach to build...", "document the approach for...", "create a roadmap for...", "spec this out", "write requirements for...". NOT for: code implementation (use job-orchestrator), code review (use code-review skills).

mrciphersmith Bundle

Defines core problems, goals, non-goals, and success metrics from discovery data. Use when: dispatched by gproject-orchestrator Phase 1. NOT for: direct user invocation.

keyvaluesoftwaresystems Skill

Write or narrowly repair one decision-focused HLD from an approved PRD, maintained architecture context, and confirmed technical decisions in plain, skimmable technical English.

keyvaluesoftwaresystems Skill

Write or repair one final PRD from fully confirmed structured context in plain, skimmable technical English. Use only after the PRD interview is complete; never invent missing product decisions.

keyvaluesoftwaresystems Skill

Clarify product intent before a PRD is written. Summarize maintained project context, confirm the feature goal, generate feature-specific Grill questions, and resolve material behaviour and edge cases without scanning application code or drafting the PRD.

keyvaluesoftwaresystems Skill

Convert legacy PRD and HLD documents into current concise structures while preserving every existing decision and adding no new product or architecture content.