skills.rest
YunosukeYoshino
YunosukeYoshinoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-harness-bridge

Generate a prompt, spec, plan, and sprint contract under the work/ directory.

Updated Apr 3, 2026
Search Tags:#workflow#planning#handoff#spec#prompts#spec-first
One-click install
npx skills add https://github.com/YunosukeYoshino/harness --skill spec-harness-bridge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-harness-bridge
Source: https://github.com/YunosukeYoshino/harness/tree/main/.claude/skills/spec-harness-bridge
Command: npx skills add https://github.com/YunosukeYoshino/harness --skill spec-harness-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-first workflow helps teams convert user requests into well-defined artifacts (prompt, spec, plan, sprint contract) before implementing code, reducing rework and clarifying scope.

Core Features & Use Cases

  • Generates and stores the artifacts under work/specs/active, work/plans/active, and work/sprint-contracts/active for a given slug.
  • Reads repository constraints (AGENTS.md, CLAUDE.md, docs/repo-map.md, docs/architecture/system-overview.md, and work/README.md) to ensure feasibility.
  • Facilitates handoff to dev by isolating specification from implementation and providing a clear plan.

Quick Start

Provide a user request and let the skill generate the prompt, spec, plan, and sprint contract under the work/ directory.

Frequently Asked Questions about spec-harness-bridge

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

FAQPage Schema
How do I convert a user request into a structured spec-first workflow?▼

A spec-first workflow translates a user request into structured artifacts like a prompt, spec, plan, and sprint contract before coding, reducing rework and clarifying scope for development handoff.

How do I generate a sprint contract and plan from a prompt?▼

You generate a sprint contract by providing a user request; the skill automatically creates the contract, spec, and plan in work/sprint-contracts/active and work/plans/active using a specific slug.

Does this spec-first workflow read repository constraints like AGENTS.md?▼

Yes, the workflow reads repository constraints including AGENTS.md, CLAUDE.md, docs/repo-map.md, and docs/architecture/system-overview.md to ensure generated plans and specs remain feasible within your architecture.

What is the best way to isolate specification from implementation for dev handoff?▼

The best way to isolate specification from implementation is generating structured artifacts under the work/ directory, providing a ready handoff to development by clarifying scope and reducing rework.

Can I use this spec generation process without existing docs/repo-map.md or work/README.md files?▼

The process is designed to respect repository constraints like docs/repo-map.md and work/README.md to ensure feasibility, so lacking these files may limit its ability to align outputs with existing architecture conventions.

Related Skills

Explore More Software Engineering Skills→
latitude-devlatitude-dev
4.6k

docs

Archive session decisions and repo changes into structured docs and AGENTS.md.

Official
Advanced
jineynejineyne

speckit-plan

Generate implementation plans and design artifacts from spec-kit repositories.

Community
Advanced
istota-projectistota-project
10

spec

Draft and manage feature specifications across Drafts, Active, and Done lifecycle folders.

Official
Advanced
alibabaalibaba
136

speckit.plan

Generate project implementation plans with design artifacts from feature specifications.

Official
Intermediate