Project Specification

Name: Project Specification
Author: athola

athola/claude-night-market

133 installs
325 repo stars
Updated August 2, 2026
athola/claude-night-market

Turn a post-brainstorm project brief into testable specs with user stories, acceptance criteria, and clear in/out-of-scope boundaries before implementation planning.

About

Project Specification is a workflow skill for solo builders who have direction from brainstorming but lack implementation-ready requirements. It converts a project brief into structured specifications: user stories, acceptance criteria you can test, scope boundaries, and enough technical framing to feed planning and QA. The skill is intermediate complexity and prefers Claude Sonnet-class models for balanced prose and structure. It integrates with the broader attune night-market flow—brainstorm first, specify second, plan third—and delegates heavyweight spec-kit methodology to spec-kit:spec-writing when you need canonical templates and validation. Use it when business intent exists but engineers (or your agent) would otherwise guess at edge cases. Skip it when you are still exploring the problem space or when a detailed spec already exists and you only need task breakdown.

Transforms project briefs into testable specifications with user stories and acceptance criteria
Defines in-scope and out-of-scope items before implementation
Delegates deep spec methodology to spec-kit:spec-writing when documents need to be thorough
Explicit handoff: after brainstorming completes, before project-planning
Supports planning validation and testing strategy at the requirements layer

Project Specification by the numbers

133 all-time installs (skills.sh)
Ranked #1,237 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
Security screen: LOW risk (skills.sh audit)
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/athola/claude-night-market --skill project-specification

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/athola/claude-night-market/project-specification.svg)](https://skillselion.com/skills/athola/claude-night-market/project-specification)

Installs	133
repo stars	★ 325
Security audit	3 / 3 scanners passed
Last updated	August 2, 2026
Repository	athola/claude-night-market ↗

What it does

Turn a post-brainstorm project brief into testable specs with user stories, acceptance criteria, and clear in/out-of-scope boundaries before implementation planning.

Files

SKILL.mdMarkdownGitHub ↗

Delegation

For detailed specification writing workflows, this skill delegates to spec-kit:spec-writing as the canonical implementation. Use this skill for quick specification needs; use spec-kit for thorough specification documents.

When To Use

After brainstorming phase completes
Have project brief but need detailed requirements
Need testable acceptance criteria for implementation
Planning validation and testing strategy
Translating business requirements into technical specs
Defining scope boundaries and out-of-scope items

When NOT To Use

Still exploring problem space (use Skill(attune:project-brainstorming) instead)
Already have detailed specification (use Skill(attune:project-planning) instead)
Refining existing implementation (use code review skills)
Making strategic decisions (use Skill(attune:war-room) for complex choices)

Integration

With spec-kit:

Delegates to Skill(spec-kit:spec-writing) for methodology
Uses spec-kit templates and validation
Enables clarification workflow

Without spec-kit:

Standalone specification framework
Requirement templates
Acceptance criteria patterns

Record the Tradeoff (decision journal)

If the specification settled a design decision with real alternatives (a chosen data model, an interface boundary, a constraint accepted), record it to docs/tradeoffs.md before continuing (draft and confirm):

If leyline is installed, invoke Skill(leyline:decision-journal) and append

a tradeoff entry (the decision, the options weighed, and what was sacrificed; set phase to specify). Show the draft; append on confirmation.

Fallback (leyline absent): append to docs/tradeoffs.md using the in-file

ENTRY TEMPLATE; assign the next TR-NNN id.

Post-Completion: Workflow Continuation (REQUIRED)

Automatic Trigger: After Quality Checks pass and docs/specification.md is saved, MUST auto-invoke the next phase.

When continuation is invoked: 1. Verify docs/specification.md exists and is non-empty 2. Display checkpoint message to user:

   Specification complete. Saved to docs/specification.md.
   Proceeding to planning phase...

3. Invoke next phase:

   Skill(attune:project-planning)

Bypass Conditions (ONLY skip continuation if ANY true):

--standalone flag was provided by the user
docs/specification.md does not exist or is empty (phase failed)
User explicitly requests to stop after specification

Do NOT prompt the user for confirmation: this is a lightweight checkpoint, not an interactive gate. The user can always interrupt if needed.

Exit Criteria

[ ] docs/specification.md exists, is non-empty, and passes Quality Checks.
[ ] Every functional requirement has testable acceptance criteria.
[ ] Any design decision with real alternatives is recorded to

docs/tradeoffs.md (or there was no meaningful design fork).

[ ] The next phase is auto-invoked unless a bypass condition holds.

Related Skills

Skill(spec-kit:spec-writing) - Spec-kit methodology (if available)
Skill(attune:project-brainstorming) - Previous phase
Skill(attune:project-planning) - AUTO-INVOKED next phase after specification
Skill(attune:mission-orchestrator) - Full lifecycle orchestration