Summarize

Generate concept_summary.md from an idea specification for planning and traceability.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Darkpunkki/v-forge --skill summarize-darkpunkki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Summarize
Source: https://github.com/Darkpunkki/v-forge/tree/main/.claude/skills/concept-summarizer
Command: npx skills add https://github.com/Darkpunkki/v-forge --skill summarize-darkpunkki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a raw idea/spec into a stable invariant concept_summary.md that serves as the planning anchor for ongoing work, runs, and updates to the latest summary.

Core Features & Use Cases

  • Generates a dedicated concept_summary.md for each idea to serve as a persistent planning anchor during exploration and development.
  • Updates the latest concept_summary.md to reflect the current understanding of the idea, enabling quick reference.
  • Produces per-run outputs under docs/forge/ideas/<IDEA_ID>/runs/<RUN_ID>/concept_summary.md and logs activity to run_log.md for auditability and traceability.
  • Validates and uses inputs: Baseline idea spec at docs/forge/ideas/<IDEA_ID>/inputs/idea.md, optional normalized input docs/forge/ideas/<IDEA_ID>/latest/idea_normalized.md, and optional concept_config.md, to guide the summary.
  • Maintains a per-idea manifest with status and provenance.

Quick Start

Invoke the concept-summarizer with an IDEA_ID to generate a new concept_summary and update the latest anchor.

Frequently Asked Questions about Summarize

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

FAQPage Schema
How do I create a stable concept summary from a raw idea specification?▼

To create a stable concept summary from a raw idea specification, the Skill generates an invariant semantic anchor concept_summary.md. This file serves as a persistent planning anchor during ongoing exploration and development runs.

What is the best way to maintain planning traceability across multiple development runs?▼

Maintaining planning traceability across runs is achieved by generating per-run concept_summary.md files and logging activity to run_log.md. The Skill also updates a latest concept_summary.md to reflect the current idea understanding for quick reference.

How does a concept summary anchor work for project planning and traceability?▼

A concept summary anchor works by providing a persistent semantic reference point derived from an idea specification. It ensures that ongoing work and updates remain aligned with the original concept, updating the latest summary for quick reference.

Do I need a normalized idea file to generate a concept summary?▼

You do not need a normalized idea file to generate a concept summary. The Skill requires a baseline idea spec at inputs/idea.md, but optionally uses a normalized input at latest/idea_normalized.md and a concept_config.md to guide the summary output.

Can I audit changes when updating the latest concept summary for an idea?▼

You can audit changes when updating the latest concept summary because the Skill produces a run_log entry and manifest updates. It maintains a per-idea manifest with status and provenance, and logs activity to run_log.md for full auditability.

What are the limitations of using a single invariant concept summary for project planning?▼

A limitation of using a single invariant concept summary is that it applies to one specific IDEA_ID, writing outputs to dedicated run and latest directories. It relies on the initial idea specification and optional normalized inputs, which may constrain dynamic scope changes.