Add remediate-3000 and cross-sell-3000 skills#176
Open
landon-posthog wants to merge 5 commits into
Open
Conversation
Two new stepwise skills that extend the audit-3000 family: - remediate-3000: write-side companion to audit-3000. Parses posthog-audit-report.md into a classified plan and applies the safe fixes to project source (dep bumps, identity fixes, PII removal, duplicate-event removal, event-name alignment, init config, instrumentation gaps), verifying against a pre-edit baseline. Never mutates PostHog state or git; renders PostHog-side changes as copy-paste prompts. - cross-sell-3000: code-grounded product expansion. Scans the codebase to detect which PostHog products fit (greenfield, competitor cross-sell, coverage gaps), proposes and prioritizes them, plans each implementation, and scaffolds the viable ones with build verification. Both follow the existing stepwise conventions (per-file next_step, docs-only config, [STATUS]/[ABORT] lines) and write a single report file at the project root. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
…mple cap - Step 1 detect: all 8 detectors in one message (no serial batches), Explore/haiku, hard-capped greps/turns - Step 4 plan: fan out one sonnet subagent per item; orchestrator no longer pre-reads evidence - Step 5 scaffold: pin sonnet; single illustrative example per product, not full coverage - Step 6 verify: fan out read-only spot-checks on haiku when >2 items - Step 7 report: map-reduce per-item sections on haiku; short report, one line per item - Models capped at sonnet, never opus Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Minimal docs-only skill: read a bundled PostHog feature-flags guide and generate a task list. Variants: best-practices, cleaning-up-stale-flags, cutting-costs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
An interrupted run leaves /tmp plan/opportunities/env files behind (Step 7 cleanup only runs on success), and the next run reuses them — short-circuiting Steps 3-4 on stale data. Step 1 now wipes them before detection. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add an explicit instruction (and a Task list section in the remediate-3000/cross-sell-3000 style) to form a plan and call TaskCreate immediately after reading the bundled guide, before scanning the project, then refine with TaskUpdate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Author
|
@gewenyu99, you good for me to merge these? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two new stepwise skills that extend the audit-3000 family from "find problems" into "fix them" and "grow adoption":
remediate-3000— the write-side companion toaudit-3000. Parses theposthog-audit-report.mdthat audit-3000 produces into a classified remediation plan, then applies the safe fixes directly to project source: dependency bumps, identity fixes, PII removal, duplicate-event removal, event-name alignment, init-config additions, and instrumentation gap fills. Verifies every fix against a baseline recorded before any edit. Never mutates PostHog state or git — PostHog-side changes (insight edits, flag disabling) are rendered as copy-paste prompts in the report.cross-sell-3000— code-grounded product expansion. Scans the codebase to detect which PostHog products fit (greenfield adoption, competitor cross-sell, coverage gaps), proposes and prioritizes them by fit/value/effort, plans each implementation, and scaffolds the viable ones with build verification. Reads the code, not a CRM — every proposal citesfile:lineevidence. Reuses audit-3000's per-product detection map so classification stays consistent.Together with
audit-3000they form a three-skill story: audit → remediate → cross-sell.Conventions followed
references/N-*.mdwith per-filenext_stepfrontmatter; terminal stepnext_step: null).docs-onlyconfig.yamlwithdescription.mdas the SKILL.md template.[STATUS]/[ABORT]line conventions and{references}/{commandments}placeholders./tmp/intermediates.BUILD_NOTES.mddocumenting design decisions, how to build/run, and open TODOs.Verification
node scripts/build.jsbuilds both skills cleanly; the packaged zips have intact chains (preamble + continuation links on every non-terminal step, neither on the terminal step).npm testgreen (60/60).remediate-3000validated end-to-end via a real wizard run against a demo project (8 fixes verified, 2 failed-with-reason, typecheck green).Notes for review
cross-sell-3000requires no prior audit run; it detects opportunities itself.🤖 Generated with Claude Code