speck-knowledge

What problem does it solve?

This Skill eliminates the need for developers to manually sift through complex Speck specification artifacts (like spec.md, plan.md, and tasks.md) to understand feature requirements, implementation status, or project architecture. It automates the interpretation of these documents, saving significant time and reducing cognitive load, allowing you to focus on development rather than documentation parsing.

Core Features & Use Cases

• Natural Language Query: Ask questions about Speck features, requirements, progress, and architecture using plain English, without needing to know specific file paths or commands.
• Automated Artifact Interpretation: Automatically parses and extracts key information from spec.md (requirements, user stories), plan.md (technical approach, constitution checks), and tasks.md (task status, dependencies).
• Workflow Context Awareness: Understands advanced Speck workflows such as multi-repo setups, stacked PRs, and Git worktrees, providing context-aware answers.
• Use Case: Imagine you're a developer joining a new project or picking up an existing feature. Instead of spending hours reading through multiple Markdown files, you can simply ask, "What are the functional requirements for feature 005?" or "How many tasks are completed for the speck skill?" and get an instant, accurate summary, allowing you to quickly onboard or resume work.

Quick Start

What are the functional requirements for feature 005?