ps

Plugin ps from marketplace psstack in psanders/psstack. Commands read from the repo's manifest — 9 days ago.

Skills (17)

• adopt

  Adopt the psstack delivery process in the current repo by drafting (or completing) its AGENTS.md from the code — overview, commands, conventions profile, area map, compatibility surface, risk hotspots, release, expert notes, decisions — for a human to review. Migrates a vendor-specific CLAUDE.md int

• ads

  Meta (Facebook/Instagram) ads toolkit with the media-buying strategy built in, invoked as /ps:ads <subcommand>. `new` is a select-driven campaign wizard (goal → objective, conversion event, audience/geo, budget with learning-phase math, naming, copy variants, assets) that builds the campaign, ad set

• docs

  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

• executive-report

  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.

• implement

  The Implementer. Takes ONE ready GitHub issue to a pull request — but first runs the refusal check and refuses (not-ready + a note) when the issue, the repo's conventions or the environment aren't clear enough. Loads the repo's declared coding profile, writes the failing test first, makes the issue'

• issues-daily

  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.

• notify

  Call Pedro's attention when work is done or blocked — a beep, then a short spoken line (macOS `say`) saying what finished or how he can help. Invoked as /ps:notify [task] — with a task, do it and notify at the end; with none, notify at the end of the current work. Use when the user runs /ps:notify,

• post-pulse

  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 s

• 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

• record

  Record THIS session while it runs a psstack process (report, implement, review) or any other task, so it can be reviewed later with /ps:retro. Starts a run id and an append-only log in a fixed format — one short entry per step with what was done, the result, the friction and any deviation from the s

• release-card

  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.

• report

  The Reporter. Turns a bug report, idea or existing GitHub issue into one or more agent-ready issues (a Brief for humans, a Spec an implementer can follow without questions), or into nothing when it isn't ready. Also drafts the missing issue for a pull request that links none, then links it. Asks fix

• retro

  Run a retrospective on a session recorded with /ps:record and turn what went wrong into fixes to psstack. Reads the run log, checks its claims against the session's transcript (found by the run id), finds the friction, deviations, user corrections and stalls that clear the bar, and proposes one fix

• review

  The Reviewer. Reviews ONE pull request against its linked ready issue with a committee of expert subagents that see only the issue and the diff, reruns the issue's Verify and the tests, and returns one verdict — ready for human review, or blocking findings back to the Implementer — with a hard limit

• sdr

  SDR (sales development) toolkit, invoked as /ps:sdr <subcommand>. Currently implements `signal-scan` — a LinkedIn buying-intent scan (keyword/hashtag pass + job-change pass) driven by claude-in-chrome against Pedro's own logged-in session, saved to the local, git-ignored data/sdr/signals.jsonl. Othe

• today

  Your morning radar for the current repo — where every issue and PR stands in the delivery pipeline with its next command, plus PRs needing you and pending releases that shouldn't pile up. Use when the user wants to know what to pay attention to today, triage, or pick work, or runs /ps:today.

• version

  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.

Subagents (11)

• database-engineer

  Database engineer. Read-only advisor on schemas, migrations, queries, indexes, transactions and data safety. Consult when a change touches a schema, a migration, an ORM model or a query on a large table.

• performance-engineer

  Performance engineer. Read-only advisor on latency, throughput, memory, resource use and load behavior. Consult when a change touches a hot path, a loop over unbounded data, I/O, caching, concurrency or anything with a stated latency or capacity target.

• pruner

  Pruner. Read-only challenger that hunts fluff — requirements, steps, tests, findings and code the work doesn't need — and makes whoever added each one prove it with a realistic trigger. Consulted after the experts by the Reporter and the Reviewer; never adds anything.

• qa-engineer

  QA engineer. Read-only advisor on test strategy, edge cases and verification. Consult when planning or reviewing any change with observable behavior.

• realtime-comms-engineer

  Real-time communications engineer. Read-only advisor on SIP, WebRTC, RTP, SDP, NAT traversal and codecs. Consult when a change touches signaling, media, transports or interop.

• release-engineer

  Release and SRE engineer. Read-only advisor on versioning, breaking changes, upgrades, configuration, deployment, rollback and observability. Consult when a change touches a public surface, config or env vars, build or release workflows, deployment manifests, or logs and metrics.

• security-engineer

  Security engineer. Read-only advisor on authentication, authorization, secrets, untrusted input, dependencies, CI and agent safety. Consult when a change touches auth, credentials, input parsing, external calls, dependencies, CI workflows, or anything that reads text from outside the team.

• software-architect

  Software architect. Read-only advisor on module boundaries, interfaces, dependencies and how to slice work. Consult when planning or reviewing any change that touches more than one file.

• technical-writer

  Technical writer. Read-only advisor on documentation, CLI help, error and log messages, changelogs and release notes. Consult when a change alters anything a user or operator reads or does, or adds a feature people need to learn.

• ux-designer

  UX designer. Read-only advisor on user flows, interface states, error handling, copy and accessibility. Consult when a change touches a screen, a form, a CLI prompt or any other surface a person interacts with.

• visual-designer

  Visual designer. Read-only advisor on the design system, layout, typography, color and fidelity to the approved design. Consult when a change adds or alters anything people see.