jiaojie
FlaggedCreate or receive human-first AI task handoffs across chats, models, devices, and languages. Use when the user asks to hand off, export context, resume from a handoff, switch sessions while preserving work, says "交接一下", "接收交接", or supplies handoff.md, handoff.zip, handoff-audit.zip, an LCH Bundle/T0 package, OCH Snapshot, or LTM Packet. Default to one readable handoff.md; upgrade to handoff.zip only when required files must travel, and to handoff-audit.zip only for formal audit, cross-organization delivery, or proof. Preserve current intent, stop point, next action, decisions, constraints, rejected and failed paths, answered questions, materials, omissions, and revalidation needs. Do not use for generic summaries, memory lookup, hidden reasoning, completed trivial chats, or after the user declines.
references/domain-business.md
View on GitHub# Business domain guidance
Use this reference for strategy, operations, planning, commercial analysis, or organizational decisions.
Apply the core record model unchanged; this file adds capture priorities and checks, not wire fields.
## Capture priorities
- Capture the business objective, decision context, scope, horizon, success criteria, and non-goals.
- Record stakeholders, decision owners, reviewers, affected parties, and the authority each held at capture time.
- Preserve metric definitions, units, currency, period, denominator, data source, and calculation basis.
- Separate observed performance, reported figures, forecasts, scenarios, assumptions, and unknowns.
- Record strategic decisions, rejected options, failed experiments, dependencies, and reversal triggers.
- Preserve customer, market, operational, legal, security, and reputational constraints.
- Capture risks, likelihood evidence, impact, mitigations, owners, and invalidation conditions.
- Record unresolved approvals, negotiations, commitments, and decisions that remain genuinely open.
- Preserve spreadsheets, dashboards, contracts, diagrams, presentations, and signed documents as artifacts.
- Record the next analysis, approval, negotiation, experiment, or execution action and its completion criteria.
## Principals, time, and external state
- Attribute statements to executives, employees, customers, advisers, agents, tools, and external sources separately.
- Preserve conflicting stakeholder or agent positions without inventing consensus or authority.
- Attach observation and validity times to prices, forecasts, budgets, policies, staffing, and market conditions.
- Treat CRM, finance, inventory, contracts, market feeds, approvals, and operational systems as external state.
- Revalidate volatile numbers, commitments, counterparties, and regulatory facts before acting.
- Preserve non-text evidence such as financial models, signed PDFs, decks, recordings, and dashboard exports.
## Action and authorization checks
- Use the action graph for analysis, review, approval, contracting, communication, execution, and rollback.
- Place approval, compliance, funding, and external-state checks before affected execution actions.
- Do not infer authority from seniority, historical participation, copied recipients, or an earlier handoff.
- Require current authorization for contracts, payments, hiring, pricing, disclosure, outreach, or system changes.
- Never treat a forecast, recommendation, or scenario as an approved commitment.
- Keep credentials, personal data, confidential terms, and regulated information within the approved boundary.
## Handoff checks
- Verify that every number retains its unit, currency, period, source, and epistemic basis.
- Verify that current decisions and rejected options remain distinguishable.
- Verify that stakeholder authority is captured historically but revalidated for present actions.
- Verify that critical spreadsheets or contracts are embedded or honestly marked unavailable.
- Verify that external operational state and market data carry freshness requirements.
- Verify that risks and invalidation conditions remain connected to the affected decision or action.
- Verify that competing stakeholder branches are not flattened by last-write-wins behavior.
- Block high-risk execution until approval, authorization, and required external-state checks pass.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |