blog-handoff

Generate a structured handoff document and search manual from conversation transcripts.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill blog-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-handoff
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/blog-handoff
Command: npx skills add https://github.com/arthrod/conejo-skills --skill blog-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of information loss between a deep technical development session and the creation of a blog post, ensuring the writer has a clear, searchable map of the process rather than just a raw transcript.

Core Features & Use Cases

  • Search Manual Generation: Creates a structured guide with exact search keywords for transcripts, allowing writers to pinpoint specific moments of frustration, pivots, or breakthroughs.
  • Process Evolution Tracking: Maps the journey of a project through versions (v1, v2, v3), documenting the reasoning behind every technical pivot.
  • Decision Logging: Captures the why behind architectural and methodological choices, including alternatives considered and rejected.

Quick Start

Initiate the blog handoff process by providing the session transcript path and asking the agent to generate the search manual for the current project.

Frequently Asked Questions about blog-handoff

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

FAQPage Schema
How do I turn a technical development session into a blog post draft?

To turn a technical development session into a blog post draft, you analyze conversation transcripts and output files to map process evolution and decision-making chains into a structured handoff document.

What is a session handoff document for content writing?

A session handoff document is a structured map and searchable manual generated from session logs that provides content writers precise context regarding process evolution and technical decisions.

Can I track process evolution and technical pivots from conversation logs?

Yes, you can track process evolution from conversation logs by analyzing session transcripts to map the project journey through versions and document the reasoning behind every technical pivot.

Do I need session transcripts to generate a search manual for writers?

Yes, generating a search manual requires access to session logs and project directories because the manual relies on analyzing conversation transcripts to provide exact search keywords for writers.

What's the best way to document architectural decisions for knowledge management?

The best way to document architectural decisions for knowledge management is to log the alternatives considered and rejected by analyzing compaction summaries to capture the exact reasoning behind choices.

Does blog-handoff work without compaction summaries?

Blog-handoff operates by analyzing conversation transcripts, compaction summaries, and output files, so omitting compaction summaries will reduce the precision of the generated search manual and decision mapping.