skills.rest
damsac
damsacOFFICIAL
Explore all skills by this author →
GitHub

meta-workflow

Generate numbered Markdown developer journal entries with frontmatter schema.

Updated Feb 8, 2026
Search Tags:#documentation#prompts#meta-workflow#session-history#decision-trace#developer-journal
One-click install
npx skills add https://github.com/damsac/slate --skill meta-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-workflow
Source: https://github.com/damsac/slate/tree/main/.claude/skills/meta-workflow
Command: npx skills add https://github.com/damsac/slate --skill meta-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meta-workflow enables teams to create and maintain structured developer journal entries in workflows/meta/<author>/, capturing decisions, rationale, and session history to support future reference.

Core Features & Use Cases

  • Create per-author, numbered entries (000-xxx) for features, research, onboarding, and retrospectives.
  • Store context, decisions, timeline, artifacts, and next steps to preserve institutional memory.
  • Automatically link related prompts and transcripts to show thinking in actions.

Quick Start

Create a new journal by copying workflows/meta/000-template.md to workflows/meta/<author>/000-<slug>.md and begin filling the Context, Timeline, and artifacts.

Frequently Asked Questions about meta-workflow

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

FAQPage Schema
How do I create a structured developer journal for my coding sessions?▼

To create a structured developer journal, copy the 000-template.md file to a numbered, author-specific Markdown entry and populate fields like Context, Timeline, and Artifacts to capture session history and decisions.

What is the best way to document feature decisions and session rationale in Markdown?▼

Documenting feature decisions and session rationale requires a structured Markdown format with frontmatter fields like id, status, and author, alongside a consistent body structure including Context, Timeline, and Architecture Snapshot.

Can I use a structured developer journal for onboarding and retrospective reviews?▼

Yes, structured developer journals support onboarding and retrospective reviews by storing context, decisions, timeline, artifacts, and next steps to preserve institutional memory across different session types.

How does a structured developer journal capture prompts and decision traces?▼

A structured developer journal captures prompts and decision traces by automatically linking related prompts and transcripts within the entry, showing the thinking in actions alongside the timeline and architecture snapshot.

What file naming convention should I use for per-author developer journal entries?▼

Per-author developer journal entries should use a numbered naming convention like 000-<slug>.md, stored under the workflows/meta/<author>/ directory to maintain organized session history.

What sections are required in a structured developer journal body?▼

A structured developer journal body requires sections including Context, Timeline, Architecture Snapshot, Developer Patterns Observed, Artifacts, Open Questions, and What's Next to ensure comprehensive session documentation.

Related Skills

Explore More Software Engineering Skills→
hyperbolic-chyperbolic-c
5

requirement-parser

Parse YAML frontmatter from Markdown requirement files and validate required fields.

Community
Intermediate
erlebacherlebach

communication-tracker

Convert emails, chats, and screenshots into structured project timeline entries.

Community
Advanced
kok1eeekok1eee
6

handoff

Prepend a timestamped Recap and Next Actions to .claude/journal.md.

Community
Intermediate
photonics-dhlphotonics-dhl

llm-wiki

Ingest unstructured knowledge into a persistent markdown wiki with cross-links and linting.

Community
Advanced