spec-editing

Translate product intents into durable specifications in the repo's spec/ tree.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/goddard-ai/goddard --skill spec-editing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-editing
Source: https://github.com/goddard-ai/goddard/tree/main/.agents/skills/spec-editing
Command: npx skills add https://github.com/goddard-ai/goddard --skill spec-editing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill to manage and reorganize the repository's spec/ tree without touching application code.

Core Features & Use Cases

  • Translate user intents into durable spec updates, maintaining canonical spec structure.
  • Enforce the Encapsulated Sub-Specs convention and ADRs in the spec tree.
  • Start every discovery at spec/README.md and guide mitosis when a concept becomes too broad.

Quick Start

Ask the AI to update the spec/ tree to reflect a requested change, starting from spec/README.md.

Frequently Asked Questions about spec-editing

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

FAQPage Schema
How do I translate ambiguous product intents into durable specifications?

To translate product intents into durable specifications, request a spec update starting from spec/README.md. The skill enforces the canonical spec structure, placing goals, hypotheses, and constraints into spec files without touching application code.

When do I need to split or reorganize spec content in my repository?

You need to reorganize spec content when a concept becomes too broad. The skill guides spec mitosis, splitting broad concepts into Encapsulated Sub-Specs while maintaining ADRs and repository guardrails inside the spec/ tree.

How do I maintain architecture decision records and encapsulated sub-specs?

To maintain ADRs and Encapsulated Sub-Specs, apply the skill to your spec/ tree updates. It enforces these conventions during any spec creation, update, or reorganization, ensuring contextual memory and constraints are preserved.

Does spec editing modify application code or only documentation files?

Spec editing only modifies documentation files. It strictly avoids code changes, focusing entirely on refining the spec/ tree to satisfy repository guardrails while placing product intent, goals, and constraints into spec files.

What is the best way to start updating a repository's spec tree?

The best way to start updating a repository's spec tree is to begin discovery at spec/README.md. Ask the AI to update the spec/ tree to reflect your requested changes, ensuring durable spec structure and adherence to guardrails.