From posthog-pack
Execute PostHog secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "posthog secondary workflow", "secondary task with posthog".
How this skill is triggered — by the user, by Claude, or both
Slash command
/posthog-pack:posthog-core-workflow-bThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Secondary workflow for PostHog. Complements the primary workflow.
Secondary workflow for PostHog. Complements the primary workflow.
posthog-install-auth setupposthog-core-workflow-a// Step 1 implementation
// Step 2 implementation
// Step 3 implementation
| Aspect | Workflow A | Workflow B |
|---|---|---|
| Use Case | Primary | Secondary |
| Complexity | Medium | Lower |
| Performance | Standard | Optimized |
// Complete workflow example
// Error handling code
For common errors, see posthog-common-errors.
npx claudepluginhub ktiseos-nyx/claude-code-plugins-plus-skills --plugin posthog-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026