skills.rest
Cycleaddict
CycleaddictCOMMUNITY
Explore all skills by this author →
GitHub

parametric-scribe

Record project tasks in docs/recipe.yaml and replay them on new codebases.

Updated Aug 23, 2026
Search Tags:#automation#history#version-control#code-management#recipe#replay#record
One-click install
npx skills add https://github.com/Cycleaddict/parametric-scribe --skill parametric-scribe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parametric-scribe
Source: https://github.com/Cycleaddict/parametric-scribe/tree/main
Command: npx skills add https://github.com/Cycleaddict/parametric-scribe --skill parametric-scribe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parametric Scribe helps teams preserve a parametric project history in docs/recipe.yaml, enabling safe replays and intelligent repairs when changes break the current codebase.

Core Features & Use Cases

  • Recording mode appends a new entry to docs/recipe.yaml after each task, creating an auditable history.
  • Time Travel (Replay) allows resetting to a previous step, applying a new prompt, and adaptively reapplying subsequent steps with the updated codebase.
  • Forking enables creating variant histories by duplicating recipe.yaml and adjusting future steps.
  • Use Case: For long-running projects, quickly validate how changes would ripple through later steps without manual rewrites.

Quick Start

Add this folder to your Agent's workspace and tell the Agent to read parametric-scribe/SKILL.md to start coding.

Frequently Asked Questions about parametric-scribe

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

FAQPage Schema
How do I record and replay project history to rewind code changes?▼

Record and replay project history by appending tasks with fields like step_id, timestamp, and git_sha to docs/recipe.yaml, then resetting to previous steps and adaptively reapplying prompts to the updated codebase. This creates an auditable history for software projects.

What is the best way to create variant codebase histories from an existing project?▼

Forking variant histories involves duplicating docs/recipe.yaml and adjusting future steps. This enables teams to quickly validate how changes ripple through later steps without performing manual rewrites of the codebase.

Can I use this approach to adapt prompts to a new codebase base?▼

Yes, time travel replay allows resetting to a previous step, applying a new prompt, and adaptively reapplying subsequent steps. This adjusts the structured history to work with the updated codebase base automatically.

Does this recipe-based version control require specific dependencies?▼

No specific dependencies are required to manage project history with recipe.yaml. You simply add the skill folder to your Agent's workspace and instruct the Agent to read SKILL.md to start recording and replaying steps.

When do I need a parametric project history for software engineering?▼

A parametric project history is needed for long-running projects where you must rewind steps, validate how changes ripple through later steps, and repair broken codebases using structured, auditable records stored in recipe.yaml.

Related Skills

Explore More Software Engineering Skills→
az9713az9713

dark-code-suite-init

Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.

Community
Intermediate
dr-codedr-code

release-check

Run pre-release verification checks and write a versioned release assessment report.

Community
Advanced
chiruu12chiruu12
1

ship

Automate software deployment with Git branch management, testing, and pull requests.

Community
Advanced
collinarnettcollinarnett
21

git-surgical-staging

Stage precise lines from files using git diff and git apply --cached.

Community
Intermediate