Run any Skill in Manus with one click

klimkit-workflow

Stars6

Forks2

UpdatedMay 28, 2026 at 10:32

Klimkit's evidence-first Codex workflow for implementation, debugging, review, and release tasks. Use when a user asks for Klimkit, wants checklist/proof-driven work, needs `.klimkit` task artifacts, or expects verification, reflection, and final review before handoff.

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

klimentij

klimentij/klimkit

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

File Explorer

4 files

SKILL.md

readonly

name	klimkit-workflow
description	Klimkit's evidence-first Codex workflow for implementation, debugging, review, and release tasks. Use when a user asks for Klimkit, wants checklist/proof-driven work, needs `.klimkit` task artifacts, or expects verification, reflection, and final review before handoff.

Klimkit Workflow

Default Path

Prefer the Codex app for day-to-day multi-machine interaction, remote follow-up, and live thread control.
Use this plugin for reusable workflow guidance and skills.
For Git-backed plugin updates, refresh the marketplace snapshot and re-add the plugin so the local cache moves to the new version.
Use the full Klimkit repo-managed path only when the user needs machine orchestration, code-server profile projection, Switchboard, Tailscale Serve, Stop hooks, or home-level Codex config/subagent projection.

Workflow

Read the repository instructions, relevant task notes, memory/log files, and nearby tests before editing.
For implementation work, write an agent-authored acceptance checklist under .klimkit/tasks/<feature>/.
Keep edits scoped to the request and reuse existing project conventions.
Run verification that matches the blast radius. For UI work, include real screen evidence and a proof report under .klimkit/reports/.
Record meaningful verification, skipped checks, and residual risk in a task proof note.
For non-trivial work, append a timestamped reflection session to .klimkit/reflection.md after verification and before final review.
Run final review before claiming completion. Use the repository's local instructions for the required reviewer count.

References

Read references/artifact-workflow.md when the task needs concrete .klimkit task, proof, memory, log, report, or reflection layout.
Read references/repo-managed-mode.md when the user asks how the plugin differs from kk apply, Switchboard, hooks, code-server, Tailscale Serve, or repo-managed Codex config.

Keep reference loading targeted. Do not load both references by default when the body above is enough.

More from this repository

same repository

klimkit-checklister

klimentij/klimkit

Convert an implementation, debugging, release, UI, backend, security, or research request into a concrete pass/fail acceptance checklist before code changes start. Use when Codex needs blocking success criteria, scope boundaries, verification targets, or a task note for Klimkit-managed work.

2026-07-156

klimkit-diagnose

klimentij/klimkit

Diagnose bugs, failures, flaky behavior, broken tests, CI failures, or unexpected production signals with a reproduce-first workflow and Klimkit proof. Use when the user asks to debug, investigate, root-cause, fix a failure, or explain why behavior changed.

2026-07-156

klimkit-grill-me

klimentij/klimkit

Interview the user relentlessly about a plan, design, architecture, product decision, workflow, or release choice until shared understanding is reached, using repo and web research to prioritize the most important unresolved questions while recording the considered question shortlist, each asked question, and each approved decision in a Klimkit task note. Use when the user asks to be grilled, stress-test a plan, resolve design branches, clarify tradeoffs, or turn vague intent into explicit decisions.

2026-07-156

klimkit-implement

klimentij/klimkit

Run Klimkit's full implementation workflow for code, docs, release, configuration, UI, backend, security-sensitive, or proof-producing changes. Use when the user asks Codex to implement, fix, refactor, release, migrate, wire up, or complete non-trivial repository work with checklist, verification, reflection, and final review.

2026-07-156

klimkit-reflector

klimentij/klimkit

Write a concise cross-task reflection note after verification and before final review for non-trivial Klimkit work. Use when Codex should connect the current task to prior work history, patterns, risks, or future process improvements.

2026-07-156

klimkit-report-server

klimentij/klimkit

Check, explain, or set up Klimkit static proof-report serving for `docs/work` HTML reports and Tailscale URLs. Use as the fallback when native hosted publishing (Claude Code Artifacts, Codex Sites) is unavailable and a task needs report-server readiness, `/reports/` links, Tailscale Serve verification, or troubleshooting report visibility.

2026-07-156

name	klimkit-workflow
description	Klimkit's evidence-first Codex workflow for implementation, debugging, review, and release tasks. Use when a user asks for Klimkit, wants checklist/proof-driven work, needs `.klimkit` task artifacts, or expects verification, reflection, and final review before handoff.

Klimkit Workflow

Default Path

Prefer the Codex app for day-to-day multi-machine interaction, remote follow-up, and live thread control.
Use this plugin for reusable workflow guidance and skills.
For Git-backed plugin updates, refresh the marketplace snapshot and re-add the plugin so the local cache moves to the new version.
Use the full Klimkit repo-managed path only when the user needs machine orchestration, code-server profile projection, Switchboard, Tailscale Serve, Stop hooks, or home-level Codex config/subagent projection.

Workflow

Read the repository instructions, relevant task notes, memory/log files, and nearby tests before editing.
For implementation work, write an agent-authored acceptance checklist under .klimkit/tasks/<feature>/.
Keep edits scoped to the request and reuse existing project conventions.
Run verification that matches the blast radius. For UI work, include real screen evidence and a proof report under .klimkit/reports/.
Record meaningful verification, skipped checks, and residual risk in a task proof note.
For non-trivial work, append a timestamped reflection session to .klimkit/reflection.md after verification and before final review.
Run final review before claiming completion. Use the repository's local instructions for the required reviewer count.

References

Read references/artifact-workflow.md when the task needs concrete .klimkit task, proof, memory, log, report, or reflection layout.
Read references/repo-managed-mode.md when the user asks how the plugin differs from kk apply, Switchboard, hooks, code-server, Tailscale Serve, or repo-managed Codex config.

Keep reference loading targeted. Do not load both references by default when the body above is enough.