Skip to content
cccskills
FreePublished on GitHub

no-history-in-output

Apply whenever writing or updating a project-facing document — root CLAUDE.md, `.hedgehog/core-design.md`, specs, READMEs, or similar. Ensures the file reads as a clean, current, as-is snapshot rather than a log of edits or decisions. Applies on first generation and on every later revision, including "update," "rewrite," or "clean up" requests.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

No History in Output

Project-facing documents describe the current state of the thing, not the process that produced it.

Rules

  • Never include labels like "(unchanged)", "(updated)", "(new)", "(revised)", or similar edit-tracking annotations in headings or body text.
  • Never narrate the discussion that led to a decision (e.g. "we considered X but decided against it," "originally this was Y, now it's Z," "per your feedback...").
  • Never include changelogs, version history, "what changed" sections, or meta-commentary about the conversation, unless the user explicitly asks for a changelog as a deliverable in its own right.
  • Write every section as a plain statement of fact about the current design/plan/content, as if writing it fresh with full knowledge of the final decision — not as a diff against a prior version.
  • If a section documents a resolved tradeoff or an intentional design choice, state the choice and its rationale plainly (e.g. "X is an accepted tradeoff because..."), without referencing that alternatives were debated or rejected earlier in conversation.
  • An "update this doc" request re-derives a clean as-is document — it does not layer edit notes onto the previous version.

When NOT to apply

  • The user explicitly asks for a changelog, revision history, or "show me what changed."
  • The document's entire purpose is to record a process over time — a friction log entry (hedgehog friction add), a commit message, or meeting notes. Those describe what happened and when on purpose.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team

The English summary is being prepared. Showing the original description.

skyf0xx/hedgehog46Updated Oct 18, 2026

Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'

The English summary is being prepared. Showing the original description.

skyf0xx/hedgehog46Updated Oct 18, 2026

Research a topic to support a decision, three ways: draft a research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), turn a finished research report into a short summary with cited sources that other skills can use directly, or run the research here with parallel web searches. Built-in research types: market, domain, technical, competitive, user-voice, academic-lit; also supports choosing between candidates, and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between"

The English summary is being prepared. Showing the original description.

skyf0xx/hedgehog46Updated Oct 18, 2026

Test a half-formed idea in a questioning conversation, with different personas probing its weak points, until the user can act on it or drop it with confidence. Optionally writes a short brief for planning skills to build on. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'

The English summary is being prepared. Showing the original description.

skyf0xx/hedgehog46Updated Oct 18, 2026

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD

The English summary is being prepared. Showing the original description.

skyf0xx/hedgehog46Updated Oct 18, 2026

Test a product concept with Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions, ending in a complete PRFAQ document. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'

The English summary is being prepared. Showing the original description.

skyf0xx/hedgehog46Updated Oct 18, 2026

See all skills by skyf0xx

Report a problem with this skill