psstack

Recurring engagement harvest for Pedro's social posts. Opens a browser, sweeps a week or month of his LinkedIn and/or Twitter/X posts, reads each post's impressions, reactions, comments, and reposts plus a few notable comments, and saves it as structured time-series data in the psstack performance store. Promotes high performers to exemplars so /ps:post drafts from what actually works. Use when Pedro wants to measure post performance, run the weekly/monthly engagement pull, refresh the social data store, or runs /ps:post-pulse. Not for drafting posts (that's /ps:post).

Draft social posts in Pedro Sanders' voice for LinkedIn or Twitter/X, aligned with his content strategy — Voice AI infra, Fonoster, KARMA training, and Voice AI consulting. Use this skill any time Pedro asks for a post, a draft, content for the week, a hook, a carousel/thread script, a "punch up" of a draft he wrote, repurposing content from a release/changelog/customer call/talk into a post, or whenever the work is content for his personal brand on social. Trigger even when he doesn't name a network — phrases like "write a post", "tweet this", "I want to share", "draft something about [Fonoster|KARMA|Voice AI|telecom]", or "turn this into content" should all invoke this skill. Network is chosen with --network linkedin|twitter (default linkedin). Do NOT use it for long-form essays, blog posts, newsletters longer than a paragraph, marketing copy for landing pages, or generic non-Pedro creator content. Runs /ps:post.

Drive ONE OpenSpec change all the way to production-ready through fixed stages — design (Pencil) → spec reconcile → build (Storybook-first) → tests (unit + e2e) → sync → archive. Resumable across sessions via a per-change checkpoint. Use when the user wants to refine/ship/drill a single feature to done, or runs /ps:ship.

Turn raw project notes into a polished, branded biweekly executive report PDF — anonymizing teammate and customer names along the way. Use when the user wants to write an executive report, status report, or biweekly update from messy notes, or runs /ps:executive-report.

Report which version of the ps (psstack) plugin is currently running, so you can confirm whether recent skill changes have been picked up. Use when the user asks "what version", "which psstack version", "is my latest change live", or runs /ps:version.

Scaffold a new TypeScript/Node project from a captured, opinionated baseline. Presents recurring dependency groups (Prisma SQLite/Postgres, tRPC, Vite+React+Tailwind, Tauri, Expo, CLI/oclif, LangChain LLM, Storybook, docs/media, Playwright/Maestro E2E) plus opt-in workflow tooling (psstack commands, OpenSpec) as choices, confirms the stack, then scaffolds Zod-validated functions with DI + mocha/sinon tests + tooling. Use when starting a new project or service from scratch, or runs /ps:bootstrap.

Alias for /ps:today — your morning radar (issues, PRs needing you, pending releases). Kept for muscle memory; runs the today skill. Use when the user runs /ps:issues-daily.

Your morning radar for the current repo — open issues, PRs needing you, and pending releases that shouldn't pile up, grouped and ready to act on. Use when the user wants to know what to pay attention to today, triage, or pick work, or runs /ps:today.

Write or update ONE documentation page the right way — purpose narrative → sources → placement → Diátaxis-typed outline → Pencil assets → Mintlify MDX → proof → wire into nav. Resumable across sessions via a per-doc checkpoint. Use when the user wants to write, draft, or update a docs page, or runs /ps:docs.

Generate a branded release-notes card (PNG) for a repo's latest GitHub release — groups the actual commit messages by conventional-commit type and renders them as a white, social-ready changelog image with satori. Use when the user wants a shareable release image, or runs /ps:release-card.

Scaffold one function using the validated-function pattern — a factory that injects dependencies and wraps an inner fn with Zod validation + structured error handling, plus its sinon test. Use when adding a service/data function to an existing repo, or runs /ps:create-validated-function.

Daily continuous-improvement pass. Surveys the whole repo across fixed lenses, scores candidates by leverage, picks ONE high-value improvement, proposes it, and applies it on approval. Use when the user wants the daily 1%-better review, or runs /ps:kaizen.

Create a structured GitHub issue (bug, feature, or chore) in the current repo. Use when the user wants to file or report an issue, or runs /ps:issues-report.