Skill

summarize

Use when a pipeline phase completes and needs an audit trail summary. Called by other skills, not directly by users.

Install

Run in your terminal

npx claudepluginhub infraspecdev/tesseract --plugin shield

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

continuous-learning-v2

9 files

Observes Claude Code sessions via hooks to create atomic project-scoped instincts with confidence scores, evolving them into skills, commands, or agents.

ecc

144.6k

continuous-learning

2 files

Automatically extracts reusable patterns like error resolutions, workarounds, and debugging techniques from Claude Code sessions via Stop hook, saving them as learned skills for reuse.

ecc

144.6k

continuous-agent-loop

Provides patterns for continuous autonomous agent loops with loop selection, quality gates, evals, recovery controls, and failure mitigation. Useful for production AI agent workflows.

ecc

144.6k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 19, 2026

Actions

View Source View Plugin View on GitHub View README

Output Path — MANDATORY

Write the summary using the Write tool to exactly this path:

{output_dir}/{feature}/summary/{N}-{slug}/summary.md

Where {output_dir} comes from .shield.json output_dir field (default docs/shield), {feature} is the feature folder name ({feature-name}-YYYYMMDD), {N} is a sequential number, and {slug} is a short kebab-case descriptor (e.g., 1-research, 2-plan-review). Do NOT use any other path, filename, or directory. The Write tool creates directories automatically.

After writing, update {output_dir}/manifest.json and regenerate {output_dir}/index.html.

# <Phase Name> Summary **Run:** <run_id> **Date:** <timestamp> ## What was done - Bullet 1 - Bullet 2 ## Key decisions - Decision 1 (if any) ## Findings - Finding 1 (if any review findings) ## Next - What the next phase will do

Phase Summarize

Output Path — MANDATORY

Write the summary using the Write tool to exactly this path:

{output_dir}/{feature}/summary/{N}-{slug}/summary.md

After writing, update {output_dir}/manifest.json and regenerate {output_dir}/index.html.

When to Use

Called automatically by each phase's orchestrator at the end of execution. Not invoked directly by users.

Input

The orchestrator passes:

phase_name: The pipeline phase that just completed (research, plan, plan-review, sync, implement-step-N, review-step-N, final-review)
phase_output: Structured data about what was done
project_name: From .shield.json
run_id: The current run identifier (date-topic)

Process

Format the phase output as concise bullet points (5-10 bullets max)
Include: what was done, key decisions made, findings if any, next phase
Write to {output_dir}/{feature}/summary/{N}-{slug}/summary.md
Return the summary text to the orchestrator for display

Summary Format

# <Phase Name> Summary

**Run:** <run_id>
**Date:** <timestamp>

## What was done
- Bullet 1
- Bullet 2

## Key decisions
- Decision 1 (if any)

## Findings
- Finding 1 (if any review findings)

## Next
- What the next phase will do

Rules

Keep summaries concise — 5-10 bullets per section max
Include only information relevant to the next phase or audit trail
Do not repeat full review findings — reference the review summary file
Always include the "Next" section so the user knows what's coming