krypton-execution
Use when executing an approved Krypton plan, GOAL.md, or implementation plan that already defines intent, ownership, contract, cutover, task boundaries, and acceptance evidence. Use for main-agent execution with explorer, plan-reviewer, reviewer, maintainer, or verifier gates.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- krypton-execution
- description
- Use when executing an approved Krypton plan, GOAL.md, or implementation plan that already defines intent, ownership, contract, cutover, task boundaries, and acceptance evidence. Use for main-agent execution with explorer, plan-reviewer, reviewer, maintainer, or verifier gates.
02 资源文件 4
- 参考文档agents/openai.yaml295 B
- 参考文档maintainer-prompt.md687 B
- 参考文档post-plan-reviewer-prompt.md886 B
- 参考文档reviewer-prompt.md719 B
03 SKILL.md 正文
Krypton Execution
Krypton Execution runs an approved plan without drifting from its ownership, cutover, and evidence contract.
Required Roles
Use the role expectations in ../../docs/required-roles.md when the harness supports named agents. Implementation stays with the main agent. The normal execution stack is:
explorer -> main agent -> plan-reviewer -> reviewer -> maintainer -> verifier
Use the individual prompt templates in this skill folder:
post-plan-reviewer-prompt.mdreviewer-prompt.mdmaintainer-prompt.md
Entry Rule
Do not invent the plan inside this workflow. If no approved plan, goal document, or clear task board exists, ask for one direct input or use Krypton Planning first. Prefer a full Krypton goal package:
docs/goals/<goal-slug>/PLAN.md
docs/goals/<goal-slug>/GOAL.md
docs/goals/<goal-slug>/EVIDENCE.md
Before work starts, restate:
Goal:
Plan path:
Intent:
Truth owner:
Contract boundary:
Cutover:
Displaced path:
Acceptance evidence:
Kill criteria:
Forbidden moves:
Task Board
Turn the plan into an ordered board:
Task:
Owner:
Input:
Files allowed:
Files forbidden:
Output:
Evidence:
Depends on:
Parallel safe:
Run implementation tasks sequentially in the main agent unless the approved plan explicitly says otherwise.
Execution Loop
For each task:
- Confirm the task still matches the plan contract.
- Gather only the context needed for the task.
- Implement directly in the main agent.
- Review the result before integration or checkpoint.
- Check for wrong owner, duplicate path, missing cutover, contract drift, and weak proof.
- Commit or checkpoint only the current task files when the local workflow expects commits.
- Update the task board.
The main agent owns implementation, integration, and final coherence.
Evidence Gate
Do not call the goal complete because tests, lint, typecheck, or diffs passed. Those are supporting checks.
Completion requires target-perspective evidence, such as:
- UI or visual change: browser state, screenshot, or rendered output.
- API or data flow: request/response, fixture, trace, or persisted record.
- CLI or workflow: command plus important output proving the behavior.
- Migration or cutover: old path deleted, redirected, demoted, or shimmed with a removal trigger.
- Hidden logic: deterministic artifact showing the intended result.
If evidence cannot be captured, report the blocker and say implemented but unproven.
Record the accepted evidence in EVIDENCE.md before the final response when the repo uses Krypton goal packages.
Final Gates
Before final response:
- Run POST plan review when the plan had a review gate.
- Run correctness review for behavior, data integrity, trust, and missing evidence.
- Run maintainability review for duplicate paths, stale artifacts, coupling, and unclear ownership.
- Fix important findings or record why they remain.
- Summarize changed artifacts, acceptance evidence, review result, and blockers.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.