DataArt/artisyn-implementation-harness / .claude/skills/evolve
evolve
VerifiedImprove harness skills, agents, workflows, and conventions from observed friction or a concrete improvement request. Supports reflect, triage, validate, and adopt; use for harness improvements rather than ordinary product changes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
| interfaces/improvement.md | markdown | 1.2 KB |
| interfaces/reflection.md | markdown | 353 B |
| interfaces/validation.md | markdown | 653 B |
| patterns/task-tracking.md | markdown | 777 B |
| references/00-router.md | markdown | 1007 B |
| references/01-reflect.md | markdown | 805 B |
| references/02-triage.md | markdown | 2.6 KB |
| references/03-draft.md | markdown | 1.2 KB |
| references/04-validate.md | markdown | 1.5 KB |
| references/05-adopt.md | markdown | 1.5 KB |
| runtime/browser.md | markdown | 2.5 KB |
| runtime/context.md | markdown | 517 B |
| runtime/credentials.md | markdown | 512 B |
| runtime/delegation.md | markdown | 910 B |
| runtime/interaction.md | markdown | 359 B |
| runtime/planning.md | markdown | 745 B |
| runtime/review.md | markdown | 1.0 KB |
| runtime/task-tracking.md | markdown | 897 B |
runtime/planning.md
View on GitHub# Planning in Claude
If exposed and permitted, use EnterPlanMode for exploration and proposal drafting,
respect its assigned plan-file and write restrictions, and use ExitPlanMode to
present the proposal for approval. Use the interaction procedure for open decisions.
If these tools are unavailable, perform planning only without implementation;
present the proposal in conversation or an allowed planning artifact and require
the same explicit approval. State that native mode was not activated.
After actual approval and when writes are allowed, persist the identical approved
content at the workflow's project plan path. A mode exit alone is not evidence of
approval. Do not begin implementation until all workflow sign-offs are satisfied.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |