spec-cold-start

Generate structured orientation briefings with headings, chips, and status lines.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/float-ritual-stack/floatty --skill spec-cold-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-cold-start
Source: https://github.com/float-ritual-stack/floatty/tree/main/apps/outline-explorer/src/lib/skills/spec-cold-start
Command: npx skills add https://github.com/float-ritual-stack/floatty --skill spec-cold-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a quick, structured orientation briefing for a page's content, helping new readers understand context, structure, and status at a glance.

Core Features & Use Cases

  • Heading (level, content) — styled title for the briefing root
  • Chip (label, color?, icon?) — metadata tokens like project, mode, date
  • Row — horizontal container grouping chips or elements
  • StatusLine (label, color?, content) — communicates URGENT, SHIPPED, DOCTRINE, HELD
  • Paragraph — body text with additional context
  • BulletList — enumerated items to summarize key points
  • BlockRef (title, page?, blockId?) — cross-reference to other blocks/pages
  • Use cases include onboarding new team members, summarizing dense pages, or creating guided tours of documentation.

Quick Start

Generate a Cold-Start briefing for the current page using the defined components.

Frequently Asked Questions about spec-cold-start

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

FAQPage Schema
How do I create an onboarding briefing for new project documentation?

An onboarding briefing summarizes a page's structure and status using headings, chips, and status lines. It helps new readers quickly grasp context, links, and project state without reading dense paragraphs.

What is the best way to summarize a knowledge base page for new readers?

Summarizing a knowledge base page involves generating an orientation briefing with bullet lists and cross-references. This provides a structured overview of key points and connected blocks for fast comprehension.

How do I display project status and metadata at the top of a documentation page?

Display project status and metadata by using status lines and chips within an orientation briefing. Chips act as tokens for dates and modes, while status lines communicate urgent or shipped states.

Can I cross-reference other pages and blocks within a documentation briefing?

Yes, you can cross-reference other pages and blocks using the BlockRef component. This allows you to link related documentation directly within the briefing structure for guided navigation.

Does documentation onboarding require frontmatter metadata to generate a briefing?

Documentation onboarding fulfills frontmatter-driven metadata requirements to structure the briefing. The orientation layout utilizes this metadata to automatically populate headings, status lines, and component chips.

When should I not use a structured orientation briefing for my content?

Avoid a structured orientation briefing for content that requires linear narrative flow without immediate status updates. Briefings are designed for quick orientation rather than long-form, continuous reading experiences.