spec-development

Coordinate research and spec writing with templates and decision logging.

2|Updated Jan 19, 2026

Search Tags:#templates #documentation #collaboration #research #specification #review #decision-tracking

Ready to run

npx skills add https://github.com/wilddeer/specops --skill spec-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-development
Source: https://github.com/wilddeer/specops/tree/main/skills/spec-development
Command: npx skills add https://github.com/wilddeer/specops --skill spec-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps teams formalize decisions and reduce miscommunication by creating well-scoped specs before execution.

Core Features & Use Cases

Structured collaboration for spec creation with traceable decisions.
Templates for research and spec writing to standardize how work is defined.
Reusable references to ensure consistency across specs.

Quick Start

Outline the problem, collect decisions, and draft the full spec for review.

Frequently Asked Questions about spec-development

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

FAQPage Schema

How do I write a project specification before development starts?▼

Yes, structured specification templates standardize how work is defined and ensure consistency. They provide reusable references for research and drafting, making the spec creation process repeatable across different features or projects.

What's the best way to track decisions during research and specification drafting?▼

The best way to track decisions during specification drafting is to use a structured workflow with decision logging. This ensures all team choices are traceable and approved within the collaborative spec document before execution begins.

How do I coordinate team collaboration for spec creation?▼

Coordinate collaboration for spec creation by using a structured workflow with documented guidance and frontmatter-based entry points. This supports teams in formalizing decisions and drafting approved specs together before coding.

Can I standardize how work is defined across multiple specification documents?▼