thinking-reversibility
Before heavy deliberation, classify the decision as cheap or costly to undo; decide two-way doors fast and stage one-way doors to preserve options.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- thinking-reversibility
- description
- Before heavy deliberation, classify the decision as cheap or costly to undo; decide two-way doors fast and stage one-way doors to preserve options.
- disable-model-invocation
- true
03 SKILL.md 正文
Reversibility
Core rule: match process depth to undo cost. Most decisions are cheaper to reverse than they look; irreversible ones deserve deliberation and staged commitment.
When to Use
- Uncertain how much analysis a decision deserves (tech, process, product, org)
- Tempted to committee a low-blast-radius choice, or to rush a high-lock-in one
- Can redesign the move (pilot, flag, abstraction, time-box) to lower undo cost
- High-stakes choice where acting vs waiting have asymmetric recovery profiles
When NOT to Use
- Already classified this session—decide at matched depth; do not re-label forever
- Trivial two-way calls (names, local refactors) where deciding is cheaper than classifying
- Externally forced move with no optionality (hard deadline, contract, regulation)
- Correctness gates (security, data integrity) that need the right answer, not speed theater
Procedure
- Name the decision and undo path. State what would be committed and the concrete reverse move (rollback, migrate back, revoke, re-hire, re-contract).
- Score reversibility. Assess technical effort, time, money, reputation, dependents, and learning lost if reversed. Classify:
- Type 2: undo in days, low cost → decide fast
- Type 1.5: undo in weeks, moderate cost → light structure + monitor
- Type 1: months or not realistically undoable → deliberate
- Asymmetric downside / recovery. For Type 1 or 1.5:
- Acting wrong: downside, recoverable?, recovery cost
- Not acting: what permanently closes (window, exclusivity, path lock)
- Rule: recoverable acting downside + permanent inaction loss → staged commit over indefinite delay; catastrophic or third-party harm → refuse or redesign first
- Option-preserving redesign. Prefer pilots, feature flags, interfaces, versioning, time-boxed vendor terms, or strangler slices that convert Type 1 surface into Type 2 experiments. Deliberate only the residual irreversible core.
- Match process and commit. Type 2: pick a reasonable option, ship, monitor. Type 1: document assumptions, argue the opposing case, surface to owner if stakes require it. Stop once class and commitment depth are set—do not re-analyze without new undo-cost evidence.
Output
Decision: …
Undo path: …
Class: Type 2 | 1.5 | 1 (factors: …)
Acting downside / recovery: …
Not-acting permanent loss: …
Staging / option-preserving move: …
Process depth: decide-now | pilot | full deliberation
Commitment: …
Verification
- Falsify: If "we can always change later" has no concrete undo path and cost, treat as more irreversible until proven otherwise.
- Stop: After class and process depth are set, further taxonomy is waste—execute the matched process.
- Over-application guard: Do not slow trivial Type 2 work with matrices. Do not use "two-way door" to skip verification on irreversible data, security, or public commitments.
04 同仓库更多 Skills
x-content
Create, rewrite, critique, select formats for, discover opportunities for, and learn from X/Twitter content and X Articles for a technical AI-native developer/builder account. Use when turning ideas, source posts, releases, benchmarks, results, conversations, authenticated For You or creator-watch opportunities, or project evidence into an Original, Quote, Thread, Reply, or Article; reviewing article titles/outlines/visual briefs/launch hooks; improving drafts; choosing additive contributions from live X context; or learning from own-account outcomes. Own content intelligence only; compose with agent-browser for live X state and Growth OS for discovery provenance, approvals, measurement, and publication.
writing-plans
Create detailed implementation plans for multi-step software work before editing code. Use when requirements or a specification must become concrete file-level tasks, interfaces, acceptance criteria, risks, rollout, or explicitly required validation. Default to no test creation, test modification, test execution, TDD, regression-test, or coverage work unless the user, authoritative specification, or mandatory repository policy explicitly requires testing.
systematic-debugging
Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.
skill-creator
Guide for creating and updating high-quality skills by translating workflows, conventions, and reusable processes into well-structured skills. Includes context, use case examples and spec for skills. Use this skill whenever a user asks to create, update, edit, improve, package, or troubleshoot a skill, and also for conversational questions about skills in ChatGPT (e.g., "What are skills?", "What can I use skills for?", "What are the best skill use cases for me?", "Where can I find my skills?").
reflexion
Self-refinement, multi-perspective critique, verification, and durable lesson curation adapted from NeoLabHQ Reflexion. Use when the user asks to reflect, self-review, critique, double-check, verify and improve prior work, run a rigorous review, memorize lessons, or says "then reflect" after a coding, analysis, or writing task. Supports repository-aware evidence gathering and works without subagents or Claude hooks.
ponytail
Enforce Ponytail's lazy-senior-developer approach for coding, fixing, refactoring, design, dependency choices, and explicit Ponytail modes such as review, audit, debt, gain, and help. Prefer YAGNI, existing code, standard library, native platform features, existing dependencies, low reader load, and the smallest correct diff. For source mutation, keep Causal Coding authoritative for scope, testing authorization, verification cadence, and stopping. On connected WSL/Linux targets, compose with MCP Harness Router and use `wsl-web-harness` for authoritative repository work.