writing

Write a canonical tracked plan with Linear issue pointers and linked documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hack-ink/codexlab --skill writing-hack-ink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing
Source: https://github.com/hack-ink/codexlab/tree/main/.codex/plugins/plan/skills/writing
Command: npx skills add https://github.com/hack-ink/codexlab --skill writing-hack-ink

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Planning complex tasks often stalls or drifts without a durable surface. This skill produces or revises a canonical tracked plan by writing a slim plan-authority/1 pointer on the routed Linear issue, and maintains a single linked Linear document carrying the tracked-plan/1 contract with an append-only plan-event/1 history.

Core Features & Use Cases

  • Canonical plan production and revision within the Plan plugin, ensuring stable execution intent, a defined task graph, replan policy, and bindings to both the issue and the canonical document.
  • Enforces governance by allowing only this skill to alter strategy, task graph, defaults, or replan policy.
  • Typical triggers include requests for a plan, design, or implementation decomposition when the runtime is in Plan mode.

Quick Start

Command the plan writer to decompose a multi-step task and create the tracked plan with the authority pointer and linked document.

Frequently Asked Questions about writing

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

FAQPage Schema
How do I decompose a multi-step project into a tracked executable plan?

Use a plan-authority workflow to write a canonical tracked plan with a task graph and replan policy. This creates a durable plan surface with an authority pointer and a linked document for implementation.

What is a tracked plan and when do I need one for project management?

A tracked plan is a machine-readable contract that maintains stable execution intent and append-only event history. You need one for multi-step or high-risk tasks requiring a durable plan surface before implementation.

How to maintain plan authority and prevent unauthorized task graph changes?

Maintain plan authority by enforcing governance that allows only a designated writer skill to alter strategy, task graph, defaults, or replan policy. The plan-authority pointer ensures canonical plan revision control.

Does the tracked plan workflow support linking documents to Linear issues?

Yes, the tracked plan workflow links a single Linear document carrying the tracked-plan contract to a routed Linear issue. It writes a slim plan-authority pointer on the issue to bind the canonical document.

Can I use plan mode to create implementation decomposition for high-risk tasks?

Yes, you can use plan mode to create implementation decomposition for high-risk tasks. The plan writer produces a canonical tracked plan with an authority envelope and linked document before execution.

Why does project planning drift without a durable plan surface?

Project planning drifts without a durable plan surface because there is no canonical contract to maintain stable execution intent or append-only event history. Without a tracked plan, task graphs lack enforced governance.