content-production-lifecycle

Manages source-grounded content production from audience research through publication and repurposing.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill content-production-lifecycle-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-production-lifecycle
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/experimental/content-production-lifecycle
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill content-production-lifecycle-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating articles, courses, workshops, talks, and videos often happens ad hoc, leading to unsupported claims, inconsistent narratives, and content that cannot be reused across channels. This Skill turns content creation into a repeatable, evidence-backed workflow. ## Core Features & Use Cases - Structured Discovery: Starts with 5-10 questions covering audience, channel, format, voice, evidence, scope, and reuse before any drafting begins. - Evidence Mapping: Builds a claim-to-source evidence map from primary research so every assertion is traceable. - Multi-Format Derivatives: Adapts a master asset into channel-specific derivatives instead of truncating, and tracks publication status and source freshness. - Use Case: A technical writer needs a workshop, a blog article, and a conference talk on the same topic. The Skill produces a content spec, editorial RFC, narrative arc, reviewed master asset, and tailored derivatives for each channel. ## Quick Start Use the content-production-lifecycle skill to plan and draft a source-grounded workshop on our new API, including an evidence map and derivative blog post.

Frequently Asked Questions about content-production-lifecycle

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

FAQPage Schema
How do I create source-grounded technical content with a repeatable workflow?

Start with structured discovery questions about audience, channel, and evidence, then build a claim-to-source evidence map from primary research before drafting. The workflow ends with multi-stage reviews and channel-specific derivatives rather than one-off documents.

How to repurpose one article into a workshop, talk, and video?

Draft a single master asset with a designed narrative arc, then adapt derivatives for each channel instead of truncating the original. Each derivative is reshaped for its format's audience, length, and interaction style.

What reviews should technical content pass before publication?

Content should pass technical accuracy, editorial, audience-fit, accessibility, and unsupported-claim reviews. Each claim is checked against the evidence map built during research so nothing ships without a traceable source.

When is this content workflow not the right fit?

It is designed for content creation beyond the FIAP course context and may be heavier than needed for quick one-off posts. Use it when audience, evidence, review, and repurposing must be managed as a repeatable process.

How do I keep published content sources up to date?

Record publication status, source freshness, and future update triggers for each asset. When a tracked source changes or a trigger fires, the affected claims can be revisited and the asset revised.