draft-project-description

Rewrites Linear project descriptions with measurable outcomes, boundaries, and risks from project issues.

716|31|Updated Mar 13, 2023
One-click install
npx skills add https://github.com/wimpysworld/nix-config --skill draft-project-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-project-description
Source: https://github.com/wimpysworld/nix-config/tree/main/home-manager/_mixins/agentic/assistants/skills/draft-project-description
Command: npx skills add https://github.com/wimpysworld/nix-config --skill draft-project-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linear project descriptions often lack the measurable outcomes, baselines, and precise dates that the LensAgent project-quality coach scores, leaving projects with low quality ratings and unclear scope.

Core Features & Use Cases

  • Issue-driven drafting: Reads every issue and sub-issue in a Linear project to derive outcomes, boundaries, and evidence-backed motivation.
  • Coaching gap resolution: Finds open LensAgent coaching issues and addresses each named gap in name quality, measures, and dates.
  • Controlled writes: Confirms the matched project once, then updates only the description, summary, labels, priority, and dates.
  • Use Case: Ask to rewrite the description of a Linear project, and the skill resolves the project, reads its issues, composes a scored description with numbered outcomes and baselines, and writes it after one confirmation.

Quick Start

Rewrite the Linear project description for the project named "Billing Reliability" using its issues to define measurable outcomes.

Frequently Asked Questions about draft-project-description

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

FAQPage Schema
How do I improve a Linear project's LensAgent quality score?

Invoke this skill with the project name, ID, or slug. It reads every project issue and any open LensAgent coaching issue, then rewrites the description with measurable outcomes, baselines, and a precise target date addressing each scored gap.

How to write a Linear project description from its issues?

The skill reads every issue and sub-issue in the resolved project, derives outcomes and boundaries from the complete membership, and composes a description using fixed Purpose, Motivation, Outcomes, Boundaries, and Risks headings.

Can this skill rename a Linear project or change its issues?

No. It only updates the description, summary, labels, priority, and dates of the confirmed project. It never renames the project, modifies issues or membership, or touches GitHub or Slack state.

Does the skill ask for approval before writing to Linear?

It asks exactly once, to confirm the resolved project match. After that confirmation it writes the authorised fields without further approval requests, since explicit invocation with a named project grants write authority.

What are the limitations of automated Linear project updates?

The available write operation cannot add project members or favourite the project, so those are reported as manual steps. It also leaves targetDateResolution unset because a resolution snaps the date and cannot be cleared.