1c-feature-dev

Guide end-to-end 1C feature enhancements with code analysis and architectural planning.

9|4|Updated Feb 6, 2026

Search Tags:#planning #architecture #standards #code-analysis #1c

Ready to run

npx skills add https://github.com/Diversus23/1c-feature-dev --skill 1c-feature-dev-diversus23

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 1c-feature-dev
Source: https://github.com/Diversus23/1c-feature-dev/tree/main/skills/1c-feature-dev
Command: npx skills add https://github.com/Diversus23/1c-feature-dev --skill 1c-feature-dev-diversus23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams implement complex 1C enhancements by thoroughly understanding the existing configuration, asking clarifying questions, and delivering an architecture-driven plan before coding.

Core Features & Use Cases

Analysis of existing 1C code and patterns to reveal architectural decisions
Phase-driven planning including discovery, architecture, and QA
Automatic generation of a detailed plan file at .tasks/task-[feature-name]/plan.md for implementation

Quick Start

Outline the task, ask clarifying questions, and establish a concrete plan before coding.

Frequently Asked Questions about 1c-feature-dev

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

FAQPage Schema

How do I plan a complex 1C feature enhancement before writing code?▼

Plan 1C feature enhancements by analyzing existing configurations, asking clarifying questions, and documenting an architecture-driven plan in a plan.md file before coding begins.

What is the best way to analyze existing 1C code for architectural planning?▼

Analyze existing 1C code by examining current patterns and architectural decisions, which reveals the configuration's structure and informs a phase-driven development plan.

How do I ensure new 1C features conform to established coding standards?▼

Ensure 1C coding standards conformance by applying architectural design rules and phase-driven discovery, architecture, and QA planning to guide implementation and cross-agent coordination.

Does this approach generate documentation for 1C implementation tasks?▼

Yes, this 1C feature development approach generates a detailed implementation plan file automatically at .tasks/task-[feature-name]/plan.md for cross-agent coordination.

When do I need phase-driven planning for 1C configuration changes?▼

Use phase-driven planning for 1C configuration changes when scenarios require deep understanding of existing architectures, strict adherence to coding standards, and cross-agent coordination.