Examples of Real Feature Names in Knowledge-Work-Plugins

The anthropics/knowledge-work-plugins repository defines concrete feature names like "SSO support" that serve as inputs to the product-management plugin's write-spec skill.

The anthropics/knowledge-work-plugins repository provides AI-powered skills designed to streamline product management workflows. When interacting with the product-management plugin, developers use specific real feature names in knowledge-work-plugins to trigger automated specification generation and documentation.

SSO Support as a Concrete Example

The most explicit example of a real feature name appears in the write-spec skill documentation. In product-management/skills/write-spec/SKILL.md, the repository lists SSO support as a representative feature name that users can pass to the system.

This naming convention demonstrates how concise, descriptive phrases are expected to appear in user prompts. The skill processes these strings to generate comprehensive product requirement documents (PRDs) without requiring extensive manual formatting or template setup.

Executing Slash Commands with Feature Names

To invoke the specification generator, users append the feature name directly to the slash command. The syntax follows a simple pattern where the feature name acts as the primary argument to the write-spec skill.

# Triggering the write-spec skill with a real feature name

/write-spec SSO support

When executed according to the source code implementation, the skill performs a three-step workflow:

1. Clarification: Asks targeted follow-up questions regarding target users, success metrics, and scope boundaries.
2. Context retrieval: Pulls relevant data from connected tools including project trackers, design systems, and existing knowledge bases.
3. Document generation: Produces a structured PRD containing problem statements, goals, user stories, technical requirements, and acceptance criteria.

Plugin Configuration and Manifest Files

Each plugin folder contains a .claude-plugin/plugin.json manifest that registers available skills and their expected inputs. This configuration file defines how feature names are passed to the write-spec command and provides usage examples.

# .claude-plugin/plugin.json (excerpt)

{
  "name": "product-management",
  "commands": {
    "write-spec": {
      "description": "Create a spec for a given feature name",
      "example": "/write-spec SSO support"
    }
  }
}

The manifest structure establishes the contract between user input and skill execution. By documenting "SSO support" as the example parameter, the repository provides a clear template for formatting valid feature requests that the system can process effectively.

Summary

• SSO support serves as the canonical example of a real feature name in the repository, explicitly documented in product-management/skills/write-spec/SKILL.md.
• Feature names are invoked via the /write-spec slash command followed by the descriptive phrase.
• The plugin manifest at .claude-plugin/plugin.json defines the command structure, input expectations, and usage examples.
• The system transforms these simple text inputs into comprehensive product requirement documents through automated context gathering and structured generation.

Frequently Asked Questions

What format should feature names follow in knowledge-work-plugins?

Feature names should be concise, descriptive phrases like "SSO support" that clearly identify the capability being requested. According to the source code in product-management/skills/write-spec/SKILL.md, the system accepts plain text descriptions that can be processed into structured specifications without requiring specific formatting, camelCase, or code-like syntax.

Where are real feature names defined in the repository?

The primary definition resides in product-management/skills/write-spec/SKILL.md within the product-management plugin directory. This file explicitly uses "SSO support" as a concrete example of expected input. Additional references and command schemas appear in each plugin's .claude-plugin/plugin.json manifest, which documents the expected input format for slash commands and provides working examples.

How does the write-spec skill process feature names?

The skill interprets the feature name as a seed for document generation. Upon receiving a command like /write-spec SSO support, the system initiates a workflow that gathers context from connected tools, asks clarifying questions about users and metrics, and synthesizes the information into a complete PRD containing requirements, user stories, and acceptance criteria as implemented in the knowledge-work-plugins source.

Can custom feature names be used with the write-spec skill?

Yes, while "SSO support" serves as the documented example in the repository, the skill accepts any valid descriptive phrase as a feature name. The architecture supports arbitrary feature names as long as they follow the basic text input format defined in the plugin manifest and skill documentation, allowing teams to specify domain-specific capabilities unique to their products.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}