ln-130-tasks-docs-creator

Create and validate task management README.md and kanban_board.md files for Linear integration.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-130-tasks-docs-creator-cbbkrd-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-130-tasks-docs-creator
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-130-tasks-docs-creator
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-130-tasks-docs-creator-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation and validation of essential task management documentation, ensuring consistency and proper setup for project tracking.

Core Features & Use Cases

  • Automated Documentation Creation: Generates docs/tasks/README.md with workflow rules and docs/tasks/kanban_board.md for Linear integration.
  • Structure & Content Validation: Enforces SCOPE tags, required sections, and POSIX line endings, auto-fixing violations.
  • Linear Configuration: Interactively prompts for and validates Linear Team Name, UUID, and Key, setting up counters.
  • Use Case: When starting a new project or onboarding a new team member, use this Skill to quickly establish standardized task documentation and configure Linear integration, ensuring everyone is aligned on workflow and tracking.

Quick Start

Use the ln-130-tasks-docs-creator skill to create and validate task management documentation.

Frequently Asked Questions about ln-130-tasks-docs-creator

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

FAQPage Schema
How do I automate task documentation and Linear integration setup for a new project?

Creating task documentation involves generating README.md and kanban_board.md files with enforced SCOPE tags and POSIX line endings. This Skill automates Linear configuration setup by interactively prompting for Team Name, UUID, and Key, ensuring proper task lifecycle and epic grouping management.

What is the best way to enforce structure and content validation in project management documentation?

Enforcing structure in project management documentation requires validating required sections, SCOPE tags, and POSIX line endings. This Skill automatically detects and fixes structural integrity violations in your task files, ensuring content accuracy and consistent workflow alignment.

Can I use this to configure Linear counters and manage task lifecycles for epics?

Yes, you can configure Linear counters and manage task lifecycles. The Skill interactively prompts for Linear Team Name, UUID, and Key, then validates these inputs through regex to properly group epics and define test task strategies within your project documentation.

Does the documentation validation support auto-fixing violations for POSIX line endings and SCOPE tags?

Yes, the documentation validation supports auto-fixing violations for POSIX line endings and SCOPE tags. It enforces structural integrity and content accuracy across your README.md and kanban_board.md files, automatically correcting formatting errors to maintain project tracking standards.

What limitations or prerequisites should I be aware of when setting up Linear configuration?

When setting up Linear configuration, you need valid Linear Team Name, UUID, and Key credentials ready. The setup relies on regex validation and interactive prompts, requiring accurate credential inputs to successfully establish counters and manage your task lifecycle documentation.