add-concept

Insert new concepts into plain spec files with validation.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill add-concept
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-concept
Source: https://github.com/Codeplain-ai/onboarding-flow/tree/main/.claude/skills/add-concept
Command: npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill add-concept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill simplifies the process of adding new concepts, entities, or domain terms to a plain spec file, ensuring they are correctly formatted and validated.

Core Features & Use Cases

  • Concept Definition: Add a new concept with camelCase naming and detailed descriptions.
  • Syntax Validation: Check the concept name against plain syntax rules.
  • Uniqueness Check: Ensure the concept name is not already defined in the file or imports.
  • Reference Check: Validate that any referenced concepts are already defined.
  • Circular Reference Detection: Prevent circular definitions in the spec.
  • Insertion Automation: Automatically place the concept in the correct position within the file.
  • File Reading: Re-read the file after insertion to confirm correct placement and syntax.

Quick Start

Use the `add-concept skill to define a new concept in your spec file, e.g., 'add-concept :NewConceptName: is a description of the concept.'

Frequently Asked Questions about add-concept

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

FAQPage Schema
How do I define new concepts in a plain spec file without breaking syntax?

To define new concepts in a plain spec file, use an automation tool to validate naming conventions, uniqueness, and references while ensuring correct positioning and syntax compliance.

What is the best way to prevent circular references when adding domain terms to spec files?

Preventing circular references in spec files requires validating that any referenced concepts are already defined and checking definitions against existing imports to block circular dependencies.

How to check concept name uniqueness and formatting in a spec file?

Checking concept name uniqueness and formatting involves validating camelCase naming against plain syntax rules and scanning the file and imports to ensure the concept is not already defined.

Why does my spec file fail validation after inserting a new concept?

Spec file validation fails after inserting a new concept when naming conventions are violated, references point to undefined concepts, or the concept placement breaches plain syntax rules.

Can I automate the placement of new entities within existing spec files?

You can automate the placement of new entities within spec files to ensure correct positioning, automatically inserting concepts and re-reading the file to confirm proper syntax and structure.