with one click
ln-130-tasks-docs-creator
// Creates task management docs (kanban board, workflow rules) with configured tracker integration. Use when setting up task tracking for a project.
// Creates task management docs (kanban board, workflow rules) with configured tracker integration. Use when setting up task tracking for a project.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | ln-130-tasks-docs-creator |
| description | Creates task management docs (kanban board, workflow rules) with configured tracker integration. Use when setting up task tracking for a project. |
| license | MIT |
| model | claude-sonnet-4-6 |
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Type: L2 Worker Category: 1XX Documentation Pipeline
This skill creates task management documentation: docs/tasks/README.md (task management system rules) and docs/tasks/kanban_board.md (configured tracker integration with Epic Story Counters).
Create and validate task management documentation (docs/tasks/). Generates README.md with workflow rules and kanban_board.md with tracker integration that adapts to the configured provider (linear/github/file), including interactive setup for provider-specific configuration.
This skill is a L2 WORKER invoked by ln-100-documents-pipeline orchestrator OR used standalone.
Use this skill when:
Part of workflow: ln-100-documents-pipeline ā ln-110-project-docs-coordinator ā ln-120-reference-docs-creator ā ln-130-tasks-docs-creator ā ln-140-test-docs-creator (optional)
The skill follows a 3-phase workflow: CREATE ā VALIDATE STRUCTURE ā VALIDATE CONTENT.
MANDATORY READ: Load references/docs_quality_contract.md, and references/markdown_read_protocol.md.
Optional rule catalog: load references/docs_quality_rules.json only when exact rule IDs, path matrices, or allowlisted placeholder exceptions are needed.
Phase 1: CREATE - Create tasks/README.md from template with SCOPE tags, workflow rules, configured tracker integration
Phase 2: VALIDATE STRUCTURE - Auto-fix structural violations (SCOPE tags, sections, Maintenance, POSIX)
Phase 3: VALIDATE CONTENT - Validate semantic content + provider-conditional Tracker Configuration handling (placeholder detection, provider-specific field validation, interactive user prompts). Raw placeholders are allowed only during setup for docs/tasks/README.md and docs/tasks/kanban_board.md; published output must not leak unresolved markers into any other document.
Objective: Create task management system documentation from template.
When to execute: Always (first phase)
Process:
Check if tasks/README.md exists:
pattern: "docs/tasks/README.md"ā docs/tasks/README.md already exists (preserved)Create tasks directory:
docs/tasks/ directory if it doesn't existCreate tasks/README.md from template:
references/templates/tasks_readme_template.mddocs/tasks/README.md{{DATE}} ā current date (YYYY-MM-DD)SCOPE, DOC_KIND, DOC_ROLE, READ_WHEN, SKIP_WHEN, PRIMARY_SOURCES)Notify user:
ā Created docs/tasks/README.md with task management rulesā docs/tasks/README.md already exists (preserved)Output: docs/tasks/README.md (created or existing)
Objective: Ensure tasks/README.md and kanban_board.md comply with structural requirements. Auto-fix violations.
When to execute: After Phase 1 completes (files exist or created)
Process:
Files to check: docs/tasks/README.md, docs/tasks/kanban_board.md (if exists)
For each file:
<!-- SCOPE: ... --> tag and metadata markers<!-- SCOPE: Task tracking system workflow and rules ONLY --><!-- SCOPE: Quick navigation to active tasks in Linear -->ā Auto-fixed: Added missing SCOPE tag to {filename}MANDATORY READ: Load references/questions.md for validation specs (section names, heuristics, special handling rules).
For tasks/README.md:
ā Auto-fixed: Added missing section '{section}' to tasks/README.mdFor kanban_board.md (if exists):
ā Auto-fixed: Added missing section '{section}' to kanban_board.mdFiles to check: docs/tasks/README.md, docs/tasks/kanban_board.md (if exists)
For each file:
## Maintenance header in last 20 lines## Maintenance
**Update Triggers:**
- When Linear workflow changes
- When task templates are added/modified
- When label taxonomy changes
**Last Updated:** {current_date}
ā Auto-fixed: Added Maintenance section to {filename}Files to check: docs/tasks/README.md, docs/tasks/kanban_board.md (if exists)
For each file:
ā Auto-fixed: Added POSIX newline to {filename}Log summary:
ā Structure validation completed:
tasks/README.md:
- SCOPE tag: [added/present]
- Required sections: [count] sections [added/present]
- Maintenance section: [added/present]
- POSIX endings: [fixed/compliant]
kanban_board.md:
- SCOPE tag: [added/present/skipped - file not exists]
- Required sections: [count] sections [added/present/skipped]
- Maintenance section: [added/present/skipped]
- POSIX endings: [fixed/compliant/skipped]
If violations found: ā Auto-fixed {total} structural violations
Output: Structurally valid task management documentation
Objective: Ensure each section answers its validation questions with meaningful content. Special handling for Linear Configuration (placeholder detection, user prompts, UUID/Team Key validation).
When to execute: After Phase 2 completes (structure valid, auto-fixes applied)
Process:
MANDATORY READ: Load references/questions.md ā parse sections and extract validation heuristics.
Question: "What is the Linear team configuration?"
Step 3.2.1: Check if kanban_board.md exists:
pattern: "docs/tasks/kanban_board.md"ā¹ kanban_board.md not found - skipping Linear Configuration validationStep 3.2.2: Read Linear Configuration section:
docs/tasks/kanban_board.md## Linear Configuration sectionStep 3.2.3: Placeholder Detection:
Check for placeholders:
Pattern: [TEAM_NAME], [TEAM_UUID], [TEAM_KEY]
If ANY placeholder present ā Interactive Setup Mode
If NO placeholders present ā Validation Mode
Interactive Setup Mode (if placeholders detected):
Prompt user for Team Name:
Prompt user for Team UUID:
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/Prompt user for Team Key:
/^[A-Z]{2,4}$/Replace placeholders:
[TEAM_NAME] ā {user_team_name}[TEAM_UUID] ā {user_team_uuid}[TEAM_KEY] ā {user_team_key}[WORKSPACE_URL] ā https://linear.app/{workspace_slug} (if placeholder exists)Set initial counters (if table exists):
Update Last Updated date:
[YYYY-MM-DD] ā {current_date} in Maintenance sectionSave updated kanban_board.md
Log success:
ā Linear configuration updated:
- Team Name: {user_team_name}
- Team UUID: {user_team_uuid}
- Team Key: {user_team_key}
- Next Epic Number: 1
- Next Story Number: 1
Validation Mode (if real values present, no placeholders):
Extract existing values:
Team UUID: {value} or in tableTeam Key: {value} or in tableValidate formats:
/^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$//^[A-Z]{2,4}$/If validation fails:
ā Invalid format detected in Linear Configuration:
- Team UUID: {uuid} (expected: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
- Team Key: {key} (expected: 2-4 uppercase letters)
Fix manually or re-run skill to replace with correct values.
If validation passes:
ā Linear Configuration valid (Team: {name}, UUID: {uuid}, Key: {key})
Parametric loop for 3 questions (from questions.md):
For each question in:
Validation process:
ā Section may be incomplete: {section_name}Example validation (Question 1: Linear Integration):
Heuristics:
- Contains "Linear" or "MCP" ā pass
- Mentions team ID or UUID ā pass
- Has workflow states (Backlog, Todo, In Progress) ā pass
- Length > 100 words ā pass
Check content:
- ā Contains "Linear" ā PASS
ā Section valid
No auto-discovery needed (workflow is standardized in template)
Question: "Are Epics being tracked in the board?"
If kanban_board.md exists:
Validation heuristics:
- Has "Epic" or "Epics Overview" section header ā pass
- Has table with columns: Epic, Name, Status, Progress ā pass
- OR has placeholder: "No active epics" ā pass
- Length > 20 words ā pass
Action:
ā Epic Tracking section may be incompleteIf kanban_board.md does NOT exist:
ā¹ Epic Tracking validation skipped (kanban_board.md not found)Log summary:
ā Content validation completed:
tasks/README.md:
- ā Linear Integration: valid (contains "Linear", "MCP", workflow states)
- ā Task Workflow: valid (contains state transitions)
- ā Task Templates: valid (contains template references)
kanban_board.md:
- ā Linear Configuration: {status} (Team: {name}, UUID: {uuid}, Key: {key})
- ā Epic Tracking: valid (table present or placeholder)
Output: Validated and potentially updated task management documentation with Linear configuration
docs/
āāā tasks/
āāā README.md # Task management system rules
āāā kanban_board.md # Linear integration (optional, created manually or by other skills)
Note: Kanban board updated by ln-301-task-creator, ln-302-task-replanner, ln-400-story-executor (Epic Grouping logic).
references/templates/tasks_readme_template.md ā Task management system rules templatereferences/templates/kanban_board_template.md ā Linear integration + kanban templatereferences/questions.md ā Validation questions, heuristics, special handling rules/^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/; Team Key must match /^[A-Z]{2,4}$/references/docs_quality_contract.md and references/docs_quality_rules.json for placeholder policy, SCOPE/Maintenance requirements, and allowed setup exceptions[TEAM_NAME], [TEAM_UUID], or [TEAM_KEY] found in kanban_board.md, enter interactive setup mode and prompt user; do not leave unresolved markers outside the allowlisted task docsSCOPE, metadata markers, Quick Navigation, Agent Entry, and MaintenanceReturn a normalized summary so ln-100 can run a centralized docs-quality gate without re-parsing worker prose:
{
"created_files": [
"docs/tasks/README.md",
"docs/tasks/kanban_board.md"
],
"skipped_files": [],
"quality_inputs": {
"doc_paths": [
"docs/tasks/README.md",
"docs/tasks/kanban_board.md"
],
"owners": {
"docs/tasks/README.md": "ln-130-tasks-docs-creator",
"docs/tasks/kanban_board.md": "ln-130-tasks-docs-creator"
}
},
"validation_status": "passed|passed_with_fixes|skipped"
}
MANDATORY READ: Load references/docs_generation_summary_contract.md
Accept optional summaryArtifactPath.
Summary kind:
docs-generationRequired payload semantics:
worker = "ln-130"statuscreated_filesskipped_filesquality_inputsvalidation_statuswarningsWrite the summary to the provided artifact path or return the same envelope in structured output.
created_files, skipped_files, quality_inputs, and validation_statusVersion: 7.1.0 Last Updated: 2025-01-12