skills.rest
Versent
VersentOFFICIAL
Explore all skills by this author →
WebsiteGitHub

/professor-frink:amend - Amend Checkpoint with Feedback

Record feedback at HITL checkpoints and resume execution with updated context.

Updated Jan 22, 2026
Search Tags:#feedback#logging#execution#checkpoint#amend#HITL
One-click install
npx skills add https://github.com/Versent/claude-marketplace --skill professor-frink-amend-amend-checkpoint-with-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: /professor-frink:amend - Amend Checkpoint with Feedback
Source: https://github.com/Versent/claude-marketplace/tree/main/plugins/professor-frink/skills/amend
Command: npx skills add https://github.com/Versent/claude-marketplace --skill professor-frink-amend-amend-checkpoint-with-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured method to amend HITL checkpoints by capturing and applying new feedback before continuing execution, improving guidance and traceability.

Core Features & Use Cases

  • Capture feedback at a HITL checkpoint and apply it before resuming execution
  • Create or update HITL_FEEDBACK.md with user notes and instructions for the next session
  • Update the HITL checkpoint history to reflect amendments and enable reproducibility

Quick Start

Use the /professor-frink:amend "Your feedback here" to amend the current HITL checkpoint and resume with updated context. Or run interactively: /professor-frink:amend

Please provide your feedback:

Frequently Asked Questions about /professor-frink:amend - Amend Checkpoint with Feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I amend a HITL checkpoint with new feedback before resuming execution?▼

To amend a HITL checkpoint, provide feedback interactively or as an argument. The skill records notes in HITL_FEEDBACK.md, updates checkpoint-history.json, and resumes execution with the updated context applied.

What is a HITL checkpoint amendment workflow in development and testing?▼

A HITL checkpoint amendment workflow captures user feedback at a pause point and applies it before continuing. It writes to HITL_FEEDBACK.md and checkpoint-history.json to maintain guidance and traceability across sessions.

Can I provide feedback as a command argument instead of interactive input?▼

Yes, feedback can be provided as a command argument using /professor-frink:amend "Your feedback here". It skips the interactive prompt and directly writes the instructions to HITL_FEEDBACK.md before resuming.

How do I update checkpoint history to reflect manual feedback during deployment?▼

Updating checkpoint history happens automatically when you amend the checkpoint. The skill logs the new feedback into checkpoint-history.json, ensuring the deployment workflow remains reproducible and traceable.

Does the HITL amendment process require any external dependencies or components?▼

No external dependencies or components are required to amend HITL checkpoints. The skill operates independently by writing feedback to HITL_FEEDBACK.md and updating the checkpoint-history.json file locally.

When should I amend a HITL checkpoint instead of restarting the execution workflow?▼

Amend a HITL checkpoint when you need to adjust instructions or correct context without losing progress. It updates the session notes and resumes execution, whereas restarting would discard the current checkpoint state.

Related Skills

Explore More Software Engineering Skills→
refactory-langrefactory-lang

speckit-workflows.baseline

Generate baseline-spec.md and current-state.md from codebase and git history.

Official
Advanced
masharrattmasharratt
14

cfn-intervention-system

Detect human intervention requirements in CFN Loop automation workflows.

Community
Advanced
ssimhanssimhan
1

observability

Generate structured traces and step-by-step logs for agentic workflows.

Community
Intermediate
artofrawrartofrawr
1

session-management

Preserve and resume development session context using state files and structured logs.

Community
Advanced