phase2-publish

Package validated Phase 1 lines into Phase 2 publication artifacts with evidence references.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/LinkDry/Link-Research --skill phase2-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase2-publish
Source: https://github.com/LinkDry/Link-Research/tree/main/skills/phase2-publish
Command: npx skills add https://github.com/LinkDry/Link-Research --skill phase2-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn validated Phase 1 lines into a conservative Phase 2 publication package, preserving evidence and steering updates without rewriting canonical state.

Core Features & Use Cases

  • Creates and updates Phase 2 artifacts under projects/<slug>/papers/ and STATE.md to reflect published status.
  • Maintains provenance by linking to Phase 1 evidence while isolating Phase 2 outputs.
  • Use Case: When a line is Phase 2-ready, this skill packages it for official publication while keeping Phase 1 data intact.

Quick Start

Issue the Phase 2 packaging command to convert a ready line into a publication package for the current project.

Frequently Asked Questions about phase2-publish

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

FAQPage Schema
How do I automate drafting a publication package from validated research lines?

To automate drafting a publication package, the workflow reads active project context like STATE.md and evidence references, then writes draft papers, review notes, and state updates to preserve provenance while isolating final outputs.

What conditions must a research line meet to be considered Phase 2-ready for publication?

A research line is Phase 2-ready for publication when it has a readable anchor, traceable evidence references, and no unresolved gating conditions listed in the project's STATE.md file.

How does evidence management work during the Phase 2 publication process?

Evidence management during the publication process maintains provenance by linking final draft artifacts directly to Phase 1 evidence references, ensuring underlying data remains intact and traceable without rewriting canonical state.

How do I update STATE.md to reflect a published research line without losing canonical state?

To update STATE.md without losing canonical state, the workflow appends published status and steering updates under the current project directory while preserving the original Phase 1 validated lines and evidence references.

What is the best way to package Phase 2 publication artifacts while isolating them from Phase 1 data?

The best way to package publication artifacts while isolating Phase 1 data is to generate draft papers and review notes under a dedicated projects/<slug>/papers/ directory, maintaining strict separation between validated inputs and final outputs.

Can I use this publication workflow if my project has unresolved gating conditions in STATE.md?

You cannot use this publication workflow if STATE.md contains unresolved gating conditions; the process explicitly requires all gating conditions to be cleared and evidence references to be fully traceable before execution.