Act

Skill Jed-Tech/spar-kit/Research/research/example skills/act

Specify → Plan → Act → Retain: SPAR-kit is a lightweight workflow that helps AI agents align with your intent, plan clearly, act with less drift, and retain durable project memory.

Install

npx -y skills add Jed-Tech/spar-kit --skill act

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

16 stars16 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Executes plan.md for an active change under Docs/<scope>/Specs/<change-name>/. Use after plan-change when the user approves implementation. Follows tasks in order, validates each step, retries obvious failures once, and stops to ask if blocked. Does not change spec intent without approval.

SKILL.md

3.2 KB, as published. Nobody here has run it

Implement change

Execute the plan in plan.md while strictly preserving the intent in <change-name>_spec.md. Work sequentially, validate each step, keep progress updated. Refine or reorder tasks only for correctness; do not change underlying intent without approval. No silent workarounds, no drifting from the spec.

Inputs

Docs/<scope>/Specs/<change-name>/<change-name>_spec.md
Docs/<scope>/Specs/<change-name>/plan.md
Repository code and docs

Outputs

Code changes that satisfy <change-name>_spec.md
Updated plan.md with progress
Proposed <change-name>_spec.md updates (for approval only—do not apply without approval)

Workflow

1. Load context

Read <change-name>_spec.md and plan.md
Confirm scope and change folder
Identify current progress (checked tasks)

2. Execute tasks in order

For each unchecked task:

Understand the task and affected files
Implement the change
Validate (build/run/tests or targeted checks as appropriate)
Mark the task complete in plan.md

Proceed sequentially unless reordering is clearly required for correctness.

3. Validation

Prefer targeted checks when a full build is unnecessary
Ensure changes align with Success Criteria in <change-name>_spec.md
Ask the user to test or validate only if the agent cannot run the needed checks

4. Failure handling

If a task fails:

Fix obvious issues and retry once
If still failing: stop, explain the blocker, propose next steps, ask how to proceed

Do not introduce workarounds that change intent or degrade quality without approval.

5. Task evolution (allowed)

Refine wording for clarity
Split tasks into smaller steps
Reorder tasks if needed for correctness

Do not alter task intent in a way that would change the spec.

6. Spec change handling

If implementation reveals incorrect assumptions, missing constraints, or a better approach that changes intent:

Propose the spec update clearly
Do not implement that divergent path yet
Wait for user approval
Update <change-name>_spec.md only after approval

7. Keep context accurate

Keep plan.md in sync with progress
Add brief notes for edge cases, follow-ups, or partial work

Stop conditions

Stop and ask if:

A task cannot be completed after one retry
A required spec change is identified
The task list is insufficient or conflicts with the spec

Completion

Implementation is complete when:

All tasks are completed or explicitly resolved
Code satisfies Success Criteria in <change-name>_spec.md
No unresolved blockers remain

Then:

Summarize: tasks completed, deviations or notes, validation results. Be concise.
Ask: Should I clean up and proceed with documentation?
If yes: begin the document-change skill if available; otherwise document per repo conventions