nova-product

Align roadmap decisions with canonical Nova product guidance from external docs.

31|2|Updated Jun 7, 2025
One-click install
npx skills add https://github.com/shawnduggan/nova --skill nova-product
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nova-product
Source: https://github.com/shawnduggan/nova/tree/main/.claude/skills/nova-product
Command: npx skills add https://github.com/shawnduggan/nova --skill nova-product

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures durable product guidance from Nova's external product docs to keep roadmap and spec work aligned with official intent.

Core Features & Use Cases

  • Centralizes authoritative product guidance from external docs for decision-making.
  • Supports evaluating roadmaps, writing product-facing docs, and prioritizing feature work with guardrails.
  • Real-world example: When planning a feature, consult Canonical External Docs to ensure alignment with Nova's product strategy.

Quick Start

Review the Canonical External Docs and align your roadmap ideas with the official Nova product guidance.

Frequently Asked Questions about nova-product

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

FAQPage Schema
How do I align roadmap decisions with official product guidance?

Aligning roadmap decisions with official product guidance requires surfacing durable context from canonical external docs, enforcing shipped-versus-planned guardrails to keep priorities anchored to official strategy.

What is the best way to evaluate roadmap ideas against external product documentation?

Evaluating roadmap ideas against external product documentation involves referencing canonical docs to centralize authoritative guidance, applying guardrails to distinguish shipped features from planned work during prioritization.

Can I use this to review specs and write product-facing docs for planning cycles?

Yes, you can use it to review specs and write product-facing docs by extracting durable product context from external documentation, ensuring written materials align with canonical guidance across planning cycles.

How do I prioritize feature work using canonical external product docs?

Prioritizing feature work using canonical external product docs involves consulting official guidance to evaluate ideas, applying guardrails to verify shipped versus planned status, and anchoring decisions to durable product strategy.

Does this approach enforce guardrails for distinguishing shipped versus planned features?

Yes, this approach enforces shipped-versus-planned guardrails by referencing canonical external documentation, preventing misalignment between roadmap priorities and the actual status of official product features.