spec-standard

Enforce RFC 2119-compliant 1C specifications in SDD format with JSON task files.

87|15|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/SteelMorgan/1c-agent-based-dev-framework --skill spec-standard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-standard
Source: https://github.com/SteelMorgan/1c-agent-based-dev-framework/tree/main/framework/skills/spec-writing/spec-standard
Command: npx skills add https://github.com/SteelMorgan/1c-agent-based-dev-framework --skill spec-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a universal standard for writing 1C development specifications in the Spec-Driven Development (SDD) format, ensuring clarity, completeness, and adherence to best practices like RFC 2119.

Core Features & Use Cases

  • Standardized Structure: Provides a mandatory template for all specifications, covering context, requirements, scope, design, and testing.
  • RFC 2119 Compliance: Ensures requirements are clearly defined using MUST, SHOULD, MAY, and MUST NOT keywords.
  • Quality Checklist: Includes a comprehensive checklist for reviewing specification quality before implementation.
  • Task Breakdown Enforcement: Mandates task decomposition into a separate JSON file, linking it to the main specification.
  • Use Case: When starting a new feature development in 1C, use this skill to generate a compliant SDD template, ensuring all necessary sections are addressed and requirements are clearly articulated.

Quick Start

Use the spec-standard skill to generate a new specification document following the defined structure and RFC 2119 guidelines.

Frequently Asked Questions about spec-standard

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

FAQPage Schema
What is the Spec-Driven Development format for 1C specifications?

The Spec-Driven Development (SDD) format standardizes 1C specifications by enforcing a mandatory structure covering context, requirements, scope, design, and testing. It ensures clarity and completeness using RFC 2119 requirement phrasing and quality checklists.

How do I write 1C development specifications using RFC 2119?

To write 1C development specifications using RFC 2119, use MUST, SHOULD, MAY, and MUST NOT keywords to define requirements. This Skill enforces a standardized SDD template ensuring requirements are clearly articulated and unambiguous.

How do I structure a 1C feature specification for subagent execution?

Structure a 1C feature specification by decomposing tasks into a separate JSON file linked to the main document. This SDD standard supports both subagent and linear execution modes, ensuring proper task breakdown and tracking.

Does the SDD specification format include a quality assurance checklist?

Yes, the SDD specification format includes a comprehensive quality assurance checklist. This checklist is used for reviewing specification clarity and completeness before implementation begins, ensuring adherence to best practices.

Can I use this SDD standard for linear development workflows?

Yes, you can use this SDD standard for linear development workflows. The specification format mandates task decomposition into separate JSON files, explicitly supporting both subagent and linear execution modes for 1C development.

Why does my 1C specification need a separate JSON file for task breakdown?

Your 1C specification needs a separate JSON file for task breakdown to enforce structured task decomposition. This SDD standard mandates linking the JSON file to the main specification, ensuring clear scope definition and execution readiness.