shipshitdev/figure-it-out
skills/figure-it-out/SKILL.md
Design an auditable playbook when no narrower one fits. Use for figure it out, a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library figure-it-outInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 31, 2026, 2:40 AM237.5s3 files scanned
SKILL.md
- name:
- figure-it-out
- description:
- Design an auditable playbook when no narrower one fits. Use for figure it out, a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work.
- disable-model-invocation:
- true
- license:
- MIT
- version:
- 1.0.0
- tags:
- playbook, migration, audit, hypothesis
- author:
- Ship Shit Dev
- source:
- https://github.com/cursor/plugins/blob/main/pstack/skills/figure-it-out/SKILL.md
- upstream_repo:
- cursor/plugins
- upstream_ref:
- main
- upstream_commit:
- bdf7aa355337
- last_synced:
- 2026-08-26
- when_to_use:
- figure it out, large migration, ambitious multi-part change, no playbook fits
Figure it out
When the task matches no pstack playbook, design one. The deliverable
before any code is the workflow itself. Bias toward more rigor.
Do not reinvent a playbook you already have. A focused single-unit task routes to Bug fix, Perf, Feature, Visual parity, Eval, or Multi-phase plan. A large or cross-cutting version of one belongs here.
Contract
Inputs:
- A large, cross-cutting, or unattended task with no narrower playbook
Outputs:
- A designed phase list, a rigor level, a decision trail, and verification against a falsifiable predicate
Creates/Modifies:
- The work the designed playbook authorizes
- A decision log via
show-me-your-work
External Side Effects:
- Whatever the designed playbook later requires
Confirmation Required:
- One checkpoint before a multi-hour run
Delegates To:
pstackprinciples index,architect,arena,show-me-your-work
Start
Open a todo list whose first item is reading
skills/pstack/references/principles.md. Then add the phases below.
Phase A: Frame
State a falsifiable done predicate, quantified scope, and a rigor level biased high. Present framing before a long run. Reversible work proceeds. A multi-hour run earns one checkpoint.
Phase B: Design the workflow
Decompose into independently-landable units. Sequence riskiest-unknown-first. Build the verification harness before the work, with a baseline from the pre-change state.
For one-way-door design decisions, run architect (it runs arena).
Skip it for mechanical work whose shape is already concrete.
Parallelize only across genuine seams. Give each worker its own worktree or branch. Write the designed phase list down.
Phase C: Run the loop
Each unit is an experiment: hypothesis, smallest change, measure on the real artifact, keep or revert. Verify each unit before the next. A verdict is VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Inconclusive is not a pass.
Phase D: Keep the audit trail
Log via show-me-your-work. Commit the trail when a reviewer needs it
to trust the result.
Phase E: Verify and hand back
Check the whole against the Phase A predicate on the real product. Encode a recurring correction as a gate, lint, check, or script.
Reply: the playbook you designed, the rigor level and why, the trail path, what's verified, what's still open.
Related Skills
shipshitdev/weekly-review
development
VerifiedTrustedCommunity
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/project-board
testing
VerifiedTrustedCommunity
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/board-sync
testing
VerifiedTrustedCommunity
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/how
development
VerifiedTrustedCommunity
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.
35SKILL.mdUpdated Aug 31, 2026