clay-list

Scan the products directory and report pipeline statuses with artifact counts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill clay-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clay-list
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-clay/skills/clay-list
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill clay-list

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill inventories a product portfolio by scanning the products/ directory and surfaces each item's current pipeline status to give teams a clear, at-a-glance view.

Core Features & Use Cases

  • Enumerates products under products/ and classifies them as parents with sub-ideas or standalone items.
  • Derives status (idea, researched, named, PRD-created, repo-created) and counts artifacts for each product.
  • Outputs a structured table, with optional repository metadata when clay.config is present, and indents sub-ideas for clarity.

Quick Start

Scan the repository's products/ directory to generate the current status table for all products and sub-ideas.

Frequently Asked Questions about clay-list

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

FAQPage Schema
How do I track product pipeline status across multiple projects in a repository?

Track product pipeline status by scanning the products/ directory to derive each item's stage—idea, researched, named, PRD-created, or repo-created—from marker files like research.md and PRD.md. The scan outputs a structured hierarchical table with artifact counts and optional repo details.

How does pipeline status detection work for parent products with sub-ideas?

Pipeline status detection works by scanning directory structures to classify items as parent products or standalone items. It reads marker files such as naming.md, PRD-MVP.md, and .repo-url, then indents sub-ideas in the generated table to clarify the hierarchy and artifact counts.

Can I generate a portfolio overview table without configuring external dependencies?

You can generate a portfolio overview table without external dependencies. The Skill scans the local products/ directory and derives statuses from internal marker files, requiring only an optional clay.config file to surface additional repository metadata.

What marker files are required to accurately derive product pipeline stages?

Required marker files for deriving product pipeline stages include research.md, naming.md, PRD.md, PRD-MVP.md, PRD-Phases.md, and .repo-url. The presence of these files in the products/ directory determines whether a product is researched, named, or has a created repository.

Does the portfolio table include repository details for each product?

The portfolio table includes repository details when a clay.config file is present. Without it, the table still generates pipeline statuses and artifact counts by scanning the directory structure and marker files, but omits the optional repository metadata.

Why are some products indented in the generated pipeline status table?

Products are indented in the pipeline status table to represent sub-ideas under parent products. The Skill scans the directory structure to identify hierarchical relationships, ensuring sub-ideas are visually nested for clearer portfolio visibility.