菜单
Use when assessing feasibility, building an implementation plan, estimating timelines, or planning resource allocation. Analyze decisions through an operational lens — map resource requirements, identify critical path dependencies, and calculate burn rates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit written content for AI-slop and LLM-generation tells, then return a senior-reviewer report with verdict, attributable findings, authenticity fixes, and a human rewrite. Use whenever the user asks to check if writing sounds AI-generated, reads like LLM slop, needs a voice review, needs an authenticity audit, or whenever reviewing applicant submissions, marketing copy, blog drafts, bios, resumes, or any published prose to confirm it reads as human-written. Also trigger on phrases like 'does this sound like AI', 'check for AI writing', 'is this too ChatGPT', 'review the voice', 'audit this copy', or 'detect AI-generated text', even when the user doesn't use the exact word 'slop'.
Assembles a session context briefing from your configured issue tracker, recent git history, and active work signals. Use when: starting a new session, resuming after a break, user says 'catch me up', 'what was I working on', 'where did I leave off', context recovery after compaction, or user asks for project orientation. Complements Claude Code's native /recap (which auto-triggers after extended idle); briefing is invoked explicitly and pulls from cross-tool sources native /recap does not aggregate.
Audit knowledge directories (.memory/, docs/, staging/, archive/) and Claude Code auto memory for stale, misplaced, or duplicated content. Generates an editable cleanup plan file, then executes approved actions after review. Use when: periodic knowledge cleanup, after project milestones, files feel scattered or disorganized, output staging feels cluttered, moving deliverables to permanent homes. Trigger phrases: consolidate knowledge, knowledge cleanup, audit knowledge directories, find stray docs, tidy up knowledge, triage outputs, review staging, clean up outputs.
Manage ephemeral .memory/ conversation state across multi-day sessions. Checkpoint todos, decisions, and questions; promote artifacts to permanent knowledge; clean up after promotion. Use when: the user says 'checkpoint', 'save working memory', 'promote working memory', 'clean up memory', wants to persist conversation artifacts for a future session, or resumes work and asks 'what were we working on' near a .memory/ directory. Do not trigger for native auto-memory operations.
Use when weighing ethical implications, assessing stakeholder impact, evaluating responsible AI practices, or considering long-term consequences. Analyze decisions through an ethical lens — evaluate who benefits and who bears risk, assess reputation trajectory, and apply moral frameworks.
Use when red-teaming ideas, stress-testing strategies, playing devil's advocate, or doing a reality check on plans. Analyze decisions through a skeptical lens — demand quantifiable proof, calculate failure probabilities, and expose hidden assumptions.
| name | advisor-operator |
| description | Use when assessing feasibility, building an implementation plan, estimating timelines, or planning resource allocation. Analyze decisions through an operational lens — map resource requirements, identify critical path dependencies, and calculate burn rates. |
| license | MIT |
| disable-model-invocation | true |
| metadata | {"author":"Backchain","version":"1.0.0"} |
Operate from execution reality. Vision without execution is hallucination. Resources are finite. Dependencies kill more projects than competition. Speed of iteration beats perfection. Ship early, measure everything, adapt fast.
Adapt your frameworks to the scale and nature of the decision. Not all decisions involve products, markets, or venture capital. Apply only the frameworks that are relevant to the specific input.
Decision/Idea to Analyze: $ARGUMENTS
Quantify actual requirements across dimensions:
Human Capital
Financial Resources
Time Resources
Infrastructure
Map dependencies and bottlenecks:
Dependency Mapping
Bottleneck Identification
Mitigation Strategies
Calculate sustainable operational tempo:
Burn Rate Components
Monthly Burn = Salaries + Infrastructure + Marketing + Operations + Buffer
Runway = Cash Available / Monthly Burn
Efficiency Metrics
Resource Sustainability
Build minimal viable everything:
MVP Principles
Feature Prioritization Matrix
High Impact | Build Now | Build Now
Low Impact | Build Later | Never Build
Low Effort High Effort
Iteration Velocity
Track what matters:
Input Metrics (controllable)
Output Metrics (measurable)
Health Metrics (sustainable)
Supplementary frameworks in references.md:
Always lead with resource reality, then show execution path. Format:
OPERATOR ASSESSMENT: [Feasibility level] RESOURCE REQUIREMENTS: [People, $, time] CRITICAL PATH: [Key dependencies and timeline] BURN PROFILE: [Monthly burn, runway months] MVP SCOPE: [Minimum viable version] EXECUTION PHASES: [Crawl → Walk → Run] OPERATIONAL RISKS: [Top 3 breaking points]