pm-iterator

Manage named value lists across product development workflows.

Updated Oct 17, 2025
One-click install
npx skills add https://github.com/x85446/claudecodetricks --skill pm-iterator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-iterator
Source: https://github.com/x85446/claudecodetricks/tree/main/skills/pm-iterator
Command: npx skills add https://github.com/x85446/claudecodetricks --skill pm-iterator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage named value lists that can be defined once and referenced across features, requirements, and tests to avoid hardcoding constants.

Core Features & Use Cases

  • Define reusable named iterators to store lists of values, avoiding hard-coded constants.
  • List, show, add, remove, rename, and delete iterators to keep data synchronized.
  • Reference iterators across Epics, Features, Requirements, and Tests to ensure consistency.

Quick Start

Create an iterator named SOFTWARE_ARCHS with values x86,amd64,arm64 and reference it by name in your features.

Frequently Asked Questions about pm-iterator

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

FAQPage Schema
How do I manage reusable value lists across product requirements and tests?

Define named iterators to store reusable value lists, avoiding hard-coded constants across features, requirements, and tests. You can list, show, add, remove, rename, and delete these iterators to keep data synchronized.

What is the naming rule for defining a named iterator in product management workflows?

Named iterators must follow the UPPER_SNAKE_CASE naming rule. This enforces consistency when defining and referencing reusable value lists across Epics, Features, Requirements, and Tests.

How do I avoid hardcoding constants when creating Epics and Features?

Create a reusable iterator, such as SOFTWARE_ARCHS with values x86, amd64, arm64, and reference it by name. This preserves a single source of truth across your product development workflows.

Can I update and rename existing named lists of values without breaking references?

Yes, you can add, remove, rename, and delete iterators to keep data synchronized. The system preserves a single source of truth across all references where the named iterator is used.

Does this iterator approach work for synchronizing test data across features?

Yes, reference iterators across Tests and Features to ensure consistency. This prevents mismatched constants by maintaining a centralized, reusable value list that updates dynamically across all linked items.

What is the best way to maintain a single source of truth for constants in product development?

Define reusable named iterators once and reference them across Epics, Features, Requirements, and Tests. This approach eliminates duplicated constants and enforces data synchronization throughout your workflows.