Verified:GitHub

autospec-story

Generate a cited product story and implementation-state report from GitHub repository evidence.

3|1|Updated Apr 29, 2026

Search Tags:#github issues #evidence synthesis #implementation status #spec reconciliation #pull request analysis #repo storytelling #product intent

Ready to run

npx skills add https://github.com/berlinguyinca/autospec --skill autospec-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autospec-story
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-story
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, jq, curl.

What problem does it solve?

It helps you understand what an existing GitHub application is becoming and what is actually implemented versus merely planned by reconciling local specs/docs with issues, pull requests, and git history.

Core Features & Use Cases

Capability-based synthesis: organizes evidence by product capability (not just issue/PR numbers) to produce a coherent narrative of the system’s direction.
Evidence vs inference separation: distinguishes claims backed by local files, issues/PRs, and commits from conclusions that are inferred or unknown.
Read-only evidence gathering: produces a cited Markdown report without editing issues, labels, branches, commits, or pull requests.
Focused “what to inspect next”: identifies high-signal gaps and recommended follow-up questions grounded in evidence.

Quick Start

Run autospec-story for the current repository with /autospec-story --output docs/autospec-story.md.

Frequently Asked Questions about autospec-story

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

FAQPage Schema

How do I understand what a GitHub repository has actually implemented versus what is planned in the specs?▼

A repo product story synthesizes evidence from local specs, GitHub issues, PRs, and git history to explain a system's direction. It organizes findings by product capability to produce a coherent narrative of what the application is becoming for engineering or product review.

How do I generate a product narrative from GitHub issues and pull requests?▼

You can scope repo storytelling and implementation status analysis using optional flags like --since and --limit during read-only evidence gathering. This focuses the cited product story report on specific recent git history and GitHub activity periods.

Do I need GitHub CLI and jq installed to analyze a repository's implementation status?▼

Yes, analyzing a repository's implementation status requires git, the GitHub CLI (gh), jq, and curl installed. These dependencies enable the read-only evidence collection workflow needed to fetch local specs, issues, PRs, and commit history for the product story report.

What is the best way to reconcile local documentation with recent git history for a product review?▼

Yes, spec reconciliation is strictly read-only and does not edit GitHub issues, labels, branches, commits, or pull requests. It only collects evidence from local specs and GitHub activity to produce a cited Markdown implementation-state report without modifying repository state.