chronicle-record

Capture and manage project decisions in a schema-validated structured format.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/argen/hornero --skill chronicle-record
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chronicle-record
Source: https://github.com/argen/hornero/tree/main/skills/chronicle-record
Command: npx skills add https://github.com/argen/hornero --skill chronicle-record

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that critical decisions made during project sessions are captured, validated, and easily accessible for future sessions and roles.

Core Features & Use Cases

  • Structured Decision Recording: Captures decisions in a structured, schema-validated format.
  • Machine-Queryable Artifacts: Creates machine-readable artifacts for future analysis and review.
  • Decision Lifecycle Management: Manages the lifecycle of decisions, including proposal, review, and commitment.
  • Type-Specific Entries: Supports different types of entries including decisions, hypotheses, stakeholders, and customers.
  • Confidence and Sourcing Tracking: Records confidence levels and sourcing of decisions for transparency.
  • Superseding Entries: Allows superseding of previous entries when decisions change.
  • Use Case: After a strategy session, use this Skill to record the decision on pricing strategy, including the rationale, alternatives considered, and validation plan.

Quick Start

To record a decision, use the command 'chronicle-record propose --title "New Pricing Strategy" --status validated --confidence 0.85 --source-role product-manager --sourcing documented --scope strategy --decision "Implement new pricing strategy X for Q3."'

Frequently Asked Questions about chronicle-record

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

FAQPage Schema
How do I track project decisions for future reference and situational awareness?

Project decisions are captured in a structured, schema-validated format to ensure they are easily accessible for future reference and situational awareness. This approach manages the decision lifecycle from proposal to commitment.

What is the best way to record decision rationale and alternatives during strategy planning?

Recording decision rationale during strategy planning involves capturing confidence levels, sourcing, and alternatives considered. This creates machine-readable artifacts for future analysis and ensures transparency in project environments.

Can I update or supersede previous project decisions when strategies change?

Yes, previous entries can be superseded when project decisions change. This decision lifecycle management allows you to propose, review, and commit updates while maintaining a clear history of stakeholders and hypotheses.

How do I document a project decision using a structured format?

You document a project decision by defining the title, status, confidence level, source role, and scope. This structured format requires validation against a strict schema and human review for accuracy.

Does this decision tracking approach support different types of knowledge management entries?

Yes, decision tracking supports different types of entries including decisions, hypotheses, stakeholders, and customers. This ensures comprehensive knowledge management across project environments.

Are there limitations to schema-validated decision recording for project management?

A limitation of schema-validated decision recording is that it requires strict validation and human review for accuracy. This ensures data integrity but means entries cannot bypass the defined structural format.