10x-new

Create a standardized change.md workspace under context/changes with kebab-case validation.

1|Updated Feb 26, 2025
One-click install
npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-new
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-new
Source: https://github.com/kryptonum-dev/fabryka-atrakcji/tree/main/.agents/skills/10x-new
Command: npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initializes a standardized workspace for a single end-to-end change so you can start research, planning, implementation, and review without manually creating the folder structure and identity file.

Core Features & Use Cases

  • Creates a change folder from a change-id: Generates context/changes/<change-id>/ with a ready-to-edit change.md identity file.
  • Derives a human title and notes seed: Uses either a humanized change-id (empty intent) or your intent text to populate the ## Notes section.
  • Enforces guardrails before writing: Validates kebab-case formatting, checks uniqueness against context/changes/ and context/archive/, and verifies the context/changes/ parent exists.

Quick Start

Ask to create a new change like 10x-new with a kebab-case change-id and a short intent about what you want to do next.

Frequently Asked Questions about 10x-new

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

FAQPage Schema
How do I bootstrap a new change folder with a standardized markdown schema?

To bootstrap a new change folder, you provide a unique kebab-case change-id to generate a `context/changes/<change-id>/` directory with a ready-to-edit `change.md` identity file.

What validation checks are required when creating a new change workspace?

Creating a change workspace requires strict kebab-case validation for the change-id, uniqueness collision checks against `context/changes` and `context/archive`, and verifying the parent directory exists.

How do I initialize a change workspace for end-to-end engineering tasks?

You initialize a change workspace for engineering tasks by supplying a kebab-case change-id and an optional intent, which populates the `change.md` file to start research, planning, and implementation.

What happens if my change-id collides with an existing or archived change?

If a change-id collides with an existing or archived change, the workspace creation is blocked by a collision check against the `context/changes` and `context/archive` directories to ensure uniqueness.

Can I use a human-readable title instead of kebab-case for my change folder?

No, you must use kebab-case formatting for the folder identity, but the system automatically derives a humanized title from the change-id or your provided intent text for the markdown notes.

Why does creating a change workspace fail when the parent directory is missing?

Workspace creation fails because the system performs an existence check for the `context/changes` parent directory before attempting any file creation to ensure a valid folder structure.