Run any Skill in Manus with one click

docs-and-handover-guardrails

Stars0

Forks0

UpdatedFebruary 24, 2026 at 13:15

Keep operator and handover documentation aligned with behavior changes. Use when upgrades alter auth flow, runner operations, API behavior, permissions, schema assumptions, or UX workflows documented in project guides.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tokamak-network

tokamak-network/24-7-playground

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	docs-and-handover-guardrails
description	Keep operator and handover documentation aligned with behavior changes. Use when upgrades alter auth flow, runner operations, API behavior, permissions, schema assumptions, or UX workflows documented in project guides.

Docs And Handover Guardrails

Update requirements

Update README.md when setup/run/operational behavior changes.
Update AGENTS.md when architecture truth, security invariants, or validation checklist changes.
Update .agents/tasks/todo.md with checklist progress and a final review note.
When runner communication or secret-flow behavior changes, update:
- docs/published/how-it-works/page.md
- docs/published/security-notes/page.md
- related guardrail skills under .agents/skills/ in the same change set.
In this repository, when updating README.md, limit edits to:
- Current Development Status
- usage commands (run/build/test/serve style command snippets)
- Do not expand README into full handover-level detail.

Content quality rules

Write all documentation in English.
Document only confirmed behavior from code and checks.
Keep wording concrete and testable.
Remove stale statements rather than layering contradictory notes.
For communication/security topics, treat docs/published/how-it-works/page.md and docs/published/security-notes/page.md as latest operator-facing source-of-truth and keep skills synchronized to them.

Completion rules

Do not claim complete until docs match implemented behavior.
Include verification evidence or explicit limitation notes when behavior is not fully verified.

More from this repository

same repository

auth-and-permission-guardrails

tokamak-network/24-7-playground

Guard authentication, authorization, and action-permission correctness in SNS workflows. Use when changing login/session flows, nonce/signature validation, owner-agent permission boundaries, or thread/request/report state transitions.

2026-03-020

upgrade-scope-triage

tokamak-network/24-7-playground

Triage and route any non-trivial upgrade request in this repository by risk, impacted boundaries, and required guardrail skills. Use when a task touches auth, runner runtime, API contracts, schema, permissions, or docs.

2026-03-010

runner-communication-protocol-guardrails

tokamak-network/24-7-playground

Define and protect protocol contracts between Runner and the LLM agent, and between Runner and SNS APIs. Use when changing runner prompts, decision/action schema, communication logs, SNS client routes, auth headers, nonce-signature logic, or request-status/tx feedback semantics.

2026-02-240

security-boundary-guardrails

tokamak-network/24-7-playground

Enforce non-negotiable security boundaries for SNS and Runner upgrades. Use when code changes can affect secrets, auth/signing, launcher access, CORS, network flows, logging redaction, or credential storage.

2026-02-240

deploy-build-guardrails

tokamak-network/24-7-playground

Prevent deploy/build failures for SNS and Runner by enforcing guardrails around Next.js render mode, Prisma/DB access timing, environment wiring, and pre-merge verification. Use when changing build scripts, route segment config (`dynamic`/`revalidate`), Prisma usage, or Vercel deployment settings.

2026-02-230

user-error-logging-guardrails

tokamak-network/24-7-playground

Define and govern SNS user-error log collection scope, source types, payload minima, and sync rules for dev-maintenance observability.

2026-02-180

name	docs-and-handover-guardrails
description	Keep operator and handover documentation aligned with behavior changes. Use when upgrades alter auth flow, runner operations, API behavior, permissions, schema assumptions, or UX workflows documented in project guides.

Docs And Handover Guardrails

Update requirements

Update README.md when setup/run/operational behavior changes.
Update AGENTS.md when architecture truth, security invariants, or validation checklist changes.
Update .agents/tasks/todo.md with checklist progress and a final review note.
When runner communication or secret-flow behavior changes, update:
- docs/published/how-it-works/page.md
- docs/published/security-notes/page.md
- related guardrail skills under .agents/skills/ in the same change set.
In this repository, when updating README.md, limit edits to:
- Current Development Status
- usage commands (run/build/test/serve style command snippets)
- Do not expand README into full handover-level detail.

Content quality rules

Write all documentation in English.
Document only confirmed behavior from code and checks.
Keep wording concrete and testable.
Remove stale statements rather than layering contradictory notes.
For communication/security topics, treat docs/published/how-it-works/page.md and docs/published/security-notes/page.md as latest operator-facing source-of-truth and keep skills synchronized to them.

Completion rules

Do not claim complete until docs match implemented behavior.
Include verification evidence or explicit limitation notes when behavior is not fully verified.