Verified:GitHub

write-plan

Decompose a 1C change design into atomic tasks with file paths and verification criteria.

151|20|Updated Feb 11, 2026

Search Tags:#agent workflow #task decomposition #openspec #1c development #design to tasks #bsl validation #file path planning

Ready to run

npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill write-plan-arman-kudaibergenov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-plan
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/write-plan
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill write-plan-arman-kudaibergenov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting a high-level design into a concrete, implementation-ready checklist is hard to do reliably, which slows down development and causes missed steps.

Core Features & Use Cases

Design-to-tasks decomposition: Breaks agreed design into atomic 2–5 minute sub-agent tasks with explicit dependencies.
Strict file-path planning: Produces tasks that reference exact file paths and the specific skills to run for each step.
Implementation sequencing: Orders tasks to move from metadata → BSL code → forms/integration → final validation.

Quick Start

Call /write-plan with the argument openspec/changes/my-feature/design.md to generate openspec/changes/my-feature/tasks.md.

Frequently Asked Questions about write-plan

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

FAQPage Schema

How do I decompose a 1C software design into an actionable task checklist?▼

To decompose a 1C software design into an actionable task checklist, you need to break the agreed design into atomic 2–5 minute sub-agent tasks with explicit dependencies, exact file paths, and verification criteria.

What is the correct sequence for implementing tasks from a 1C change design?▼

The correct implementation sequencing for 1C change design tasks moves from metadata to BSL code, then to forms and integration, and concludes with a final validation task to ensure correctness.

Can I generate a tasks.md file directly from an openspec design.md?▼

Yes, you can generate a tasks.md file directly from an openspec design.md by reading the rlm_route_context, applying strict decomposition rules, and writing the atomic tasks to openspec/changes/<feature>/tasks.md.

Do I need BSL validation as a final step in 1C task decomposition?▼

Yes, BSL validation is required as a final step in 1C task decomposition to verify the implementation. The generated checklist must end with a final validation task to ensure all code meets standards.

What is the best way to plan file paths for 1C development sub-agent tasks?▼

The best way to plan file paths for 1C development sub-agent tasks is to produce tasks that reference exact file paths and specify the exact skills to run for each step during the design-to-tasks decomposition process.