spec-context

Parse GitHub issues and project documentation to generate context.json files.

1|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/wizact/dotclaude --skill spec-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-context
Source: https://github.com/wizact/dotclaude/tree/main/wizact-marketplace/plugins/speculator/skills/spec-context
Command: npx skills add https://github.com/wizact/dotclaude --skill spec-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the initial phase of creating specifications by parsing GitHub issues/PRs and gathering relevant project context, reducing manual research and setup time.

Core Features & Use Cases

  • Input Parsing: Handles GitHub URLs, issue numbers, or raw descriptions to understand the request.
  • Contextualization: Reads project documentation (CLAUDE.md, Constitution) and historical specs to inform context gathering.
  • Exploration: Optionally launches AI agents to explore relevant code components and synthesize findings.
  • Output Generation: Creates a context.json file and drafts clarification questions for the user.

Quick Start

Use the spec-context skill to gather context for GitHub issue number 42.

Frequently Asked Questions about spec-context

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

FAQPage Schema
How do I gather project context from GitHub issues for specification creation?▼

You can gather project context by parsing GitHub issues or raw descriptions, which automatically determines directory structures and reads relevant project documentation to output a context.json file.

What is the best way to automate collecting historical specifications and documentation for AI agents?▼

Automating context gathering for AI agents involves reading project documentation like CLAUDE.md and historical specs, optionally launching exploration agents to synthesize findings from relevant code components.

Can I use raw descriptions instead of GitHub URLs to generate a context.json file?▼

Yes, you can use raw descriptions instead of GitHub URLs to generate a context.json file, as the input parsing handles both GitHub URLs, issue numbers, and unstructured text to understand the request.

Does context gathering for specifications launch exploration agents automatically?▼

Context gathering optionally launches exploration agents to explore relevant code components and synthesize information, providing an automated way to deepen project understanding beyond static documentation.

What clarification questions should I expect when gathering project context for specifications?▼

When gathering project context for specifications, the process outputs a list of drafted clarification questions for the user, targeting missing information needed to fully define the project scope.