360 Secure SkillHub
360 安全技能中心

project-specification

核心功能是将项目简报转化为包含用户故事、验收标准的可测试规格文档，可对接spec-kit实现专业规范编写。适用于头脑风暴完成后、需细化需求、制定验收标准或明确项目边界等场景；输出为docs/specification.md，默认自动触发项目规划阶段，支持--standalone等条件绕开

athola
athola
热度 62.78
最近更新 2026-08-26 21:08:23
分类：效率依赖：读写文件 / 内部调用大模型应用场景：任务管理 / 工作流 / 模板 / 报告撰写

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add nm-attune-project-specification
Metadata
name
project-specification
description
Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning
version
1.9.8
triggers
["specification","requirements","acceptance-criteria","spec-driven-development"]
metadata
{"openclaw":{"homepage":"https://github.com/athola/claude-night-market/tree/master/plugins/attune","emoji":"🦞"}}
source
claude-night-market
source_plugin
attune

Night Market Skill — ported from claude-night-market/attune. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

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 comprehensive 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

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.

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

Related Commands

  • /attune:specify - Invoke this skill
  • /attune:specify --clarify - Run clarification workflow
  • /attune:blueprint - Next step in workflow

Examples

See /attune:specify command documentation for complete examples.