'closeout' 검색 결과

Reconcile project documentation, agent rules, authorized memory, and workspace leftovers with current code and runtime behavior. Prepare a clear handoff by correcting stale information, identifying authoritative explanations, and reporting what is verified, pending, or awaiting cleanup approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Synchronizing documentation after development
• Resolving stale or conflicting agent rule files
• Preparing a handoff to another person or a fresh session

Classify agent work as ready to continue, needing human judgment, or intentionally paused. Structure decision requests with evidence, a recommended choice, and clear outcomes, then connect the recorded decision to the next responsible agent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deciding whether agent work needs human review
• Preparing decision requests with evidence and recommended choices
• Designing a dashboard for pending human decisions

Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate the post-EXECUTE closeout packet for a plan or phase. Includes archive-readiness classification, drift signal scoring, commit checkpoint recommendation, and move-on next-state recommendation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage project closeout activities. Track completion of documentation, warranties, and final inspections.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Safely close out completed Incan work after a PR is merged by verifying merge status, syncing the base branch, removing task-owned local worktrees/assets, deleting merged local/remote branches, pruning refs, and reporting dirty or ambiguous leftovers. Use when the user says /closeout, asks to clean up after a merged PR, or wants local RFC/issue branch/worktree cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produces structured markdown session continuation documents for multi-session workflows. Captures active work streams, decisions with rationale, knowledge-file deltas learned during the session, the exact files to load next conversation, ingested content, artifacts, and open items into an ingestion-optimized handoff. Carries pending KF updates and unresolved items forward across handoff chains so context never drops. Generates a closeout checklist and echoes the starter prompt to chat. Use when approaching context limits, wrapping up a session, or managing work across conversations. Trigger on: "create a handoff," "session closeout," "wrap up this session," "build session handoff," "BSH," "continue next session," "we're running out of context," "context is getting long." Do NOT use for Memory optimization, context budget analysis, project audits, deciding whether work is ready for autonomous/Claude Code execution (use rootnode-handoff-trigger-check), or summaries with no continuation intent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use to run an ADR's closeout ceremony through to the operator's attestation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide an RxJS 7 project to RxJS Next by testing existing behavior, reviewing how subscriptions start and end, and validating small batches of changes. Record approved behavior choices, verification results, and unresolved blockers in migration reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess RxJS usage and test coverage before migration
• Plan how subscriptions and cleanup should behave
• Migrate code and TestScheduler tests in small batches

Prepare a graded Claude Managed Agent for recurring schedules, event triggers, or on-demand use. Validate timing, build deployment request data, optionally include self-evaluation for each run, and document the next steps in a roadmap.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Schedule an agent to run every morning or weekly
• Prepare a curl trigger for an external event
• Add self-evaluation to each recurring run

Close out a launched Claude Managed Agent by listing its recorded components and completed phases. Refresh a shareable, self-contained HTML overview and rank the next one or two upgrades from deferred work and operational improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the components of a launched agent
• Updating a shareable agent overview page
• Choosing the next one or two upgrades

Wrap up a client project the right way — a clean handoff, a strong final impression, and the moves that turn a finished project into referrals and repeat work. Use when asked to wrap up a client project, offboard a client, end a client relationship well, or project handoff. Produces a closeout checklist (deliverables, access, final invoice, documentation), a handoff/wrap-up message, the referral/testimonial/repeat-work asks to make at the peak moment, a graceful process for ending an ongoing relationship, and how to leave the door open — so the ending builds your business instead of just stopping.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Closeout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

中文阶段收尾技能。用于完成一个阶段、准备开新对话、需要更新状态快照、冻结模块、整理已完成任务和下一步任务时。触发语包括"阶段收尾""帮我收工""准备开新对话""更新快照""冻结阶段""总结当前状态"。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Digital punch list management for construction project closeout. Track deficiencies, assign corrections, photo documentation, and completion verification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage construction punch lists for project closeout. Track deficiencies, assign corrections, and monitor completion status.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage as-built documentation for project closeout. Track drawing markups, coordinate updates, and verify completeness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automate as-built documentation and digital handover for construction. Compile project records, generate O&M manuals, create asset databases, and ensure complete project closeout.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tendering and reporting in OpenConstructionERP: prepare tender BOQs, compare bids, manage risks, and generate reports (weekly, monthly, closeout). Use when a project goes to tender or needs reporting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks for "ретро", "обзор недели", or "что было за неделю" and the department needs a fact-based closeout plus its next Area goal.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Report which local git worktrees under tmp/ are safe to close, need a human look, or are explicitly protected. Use when the user says /fleet-audit, asks what worktrees can be cleaned up, or wants a status check across all Ralph-loop/spike worktrees before running closeout on any of them.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply the Minimum Sufficient Language (MSL) principle through the MSL Kernel to write anything a reader must act on. Bind the reader and what they already know, partition facts from the machinery that produced them, emit each admitted fact as an action, a verification, a judgment, or a state, and stop when every claim is checkable and the reader can act. Use for status updates, work-in-progress reports to your own user, closeout and convergence comments, tickets, pull request and review write-ups, incident and postmortem notes, emails, memos, and any draft for readers outside the work. Also use when the user says MSL, Minimum Sufficient Language, write this for stakeholders, drop the jargon, make this readable, or asks for a paste-ready draft.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run an authorized task inside an Available Work Time (AWT) window with a shorter Closeout Grace Period (CGP), fixed deadlines, forecast checks, proportional convergence points, and a hard stop. Use when the user explicitly requests timeboxing, supplies an AWT/CGP pair, says AWT or CGP, or an applicable project policy requires the protocol. Do not invent durations or activate timeboxing merely because a task may take time.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.