一键在 Manus 中运行任何 Skill

task-execution-guardrails

星标7

分支0

更新时间2026年3月17日 06:53

Use this skill for non-trivial coding, debugging, planning, and review tasks in this workspace. It enforces direction-following, no unapproved scope expansion, and phase discipline.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

autopilotaitech

autopilotaitech/clawforge-saas-starter

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Task Execution Guardrails

Identify the job type first: audit, plan, implement, debug, or review.
Do only that job type unless the user explicitly combines phases.
Do not add dependencies, refactors, or side workflows unless required and requested.
Do not expand scope because it feels helpful.
If the task is non-trivial, inspect the codebase first before editing.
If something goes sideways, stop and re-evaluate instead of piling on fixes.

Output discipline

audit -> findings first, no code changes
plan -> ordered tasks, files, blockers, verification
implement -> requested scope only, then verify
debug -> root cause first, then fix, then verify
review -> findings first, ordered by severity

同仓库更多 Skills

同仓库

autonomous-saas-delivery

autopilotaitech/clawforge-saas-starter

Use this skill for autonomous AI SaaS products, beta-readiness, multi-tenant systems, AI wiring, or partially wired product surfaces.

2026-03-177

principal-architect

autopilotaitech/clawforge-saas-starter

Use this skill for high-level architecture of AI-first SaaS systems, especially multi-tenant products, proactive CRM systems, autonomous workflows, temporal reasoning, embeddings, and function-calling product actions.

2026-03-177

wiring-audit

autopilotaitech/clawforge-saas-starter

Use this skill when the user asks to audit, complete, or classify the wiring of an in-progress AI SaaS application, especially when pages, routes, APIs, hooks, state, or AI integrations may be partial or missing.

2026-03-177

name	task-execution-guardrails
description	Use this skill for non-trivial coding, debugging, planning, and review tasks in this workspace. It enforces direction-following, no unapproved scope expansion, and phase discipline.

Task Execution Guardrails

Identify the job type first: audit, plan, implement, debug, or review.
Do only that job type unless the user explicitly combines phases.
Do not add dependencies, refactors, or side workflows unless required and requested.
Do not expand scope because it feels helpful.
If the task is non-trivial, inspect the codebase first before editing.
If something goes sideways, stop and re-evaluate instead of piling on fixes.

Output discipline

audit -> findings first, no code changes
plan -> ordered tasks, files, blockers, verification
implement -> requested scope only, then verify
debug -> root cause first, then fix, then verify
review -> findings first, ordered by severity