agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/product/SKILL.md

product

Skill2 starsChanged 6 months agoMITView on GitHub

Feature design workflow — transform raw feature inputs (ideas, research, stakeholder requests, competitive analysis) into a structured PRD or feature brief. Applies product-manager role. Produces PRD, user stories, acceptance criteria, success metrics, and updates FEATURES.md. First step in the planning chain, precedes architecture skill and plan skill. Includes mandatory multi-reviewer feedback loop with product-manager, marketing-strategist, content-writer, and seo-engineer.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review and research.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md at the project root to identify:

    line 15
  2. Very specific:

    If the project has a FEATURES.md, read it for the current feature registry.

    line 21
  3. Distinctive:

    Read every provided document thoroughly

    line 28
  4. Distinctive:

    If the user provides a verbal description only — proceed to Step 2 to structure it through discovery

    line 29
  5. Distinctive:

    If critical signals are missing (no clear problem statement, no target user) — ask before proceeding.

    line 44
  6. Distinctive:

    If evidence is weak — flag this as a risk.

    line 56
  7. Distinctive:

    Job-to-be-Done: When [situation], I want to [motivation], so I can [outcome]

    line 62
  8. Distinctive:

    Only include categories relevant to this feature.

    line 104
  9. Distinctive:

    Write acceptance criteria for every Must-have and Should-have requirement:

    line 108
  10. Distinctive:

    Use Given/When/Then format for behavioral criteria

    line 110
  11. Distinctive:

    After the PRD/brief is approved:

    line 258
  12. Very specific:

    If FEATURES.md does not exist — create it at the project root

    line 260
  13. Distinctive:

    Add or update the feature entry:

    line 261

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Feature Design

Transform raw feature inputs into structured product documentation. This is the product design phase — no code, architecture, or engineering decisions are made here. Output feeds into the architecture skill for technical design and the plan skill for implementation planning.

Apply product-manager role for all steps below.

0. Gather Context

Read AGENTS.md at the project root to identify:

  • Product description and domain
  • Existing features and modules (to avoid duplication and understand scope)
  • Tech stack constraints (affects feasibility assessment)
  • Team structure (affects user story assignment)

If the project has a FEATURES.md, read it for the current feature registry.

1. Receive Feature Inputs

Gather all available resources describing the feature:

  • Accepted inputs: idea brief, user research, customer feedback, support tickets, competitive analysis, stakeholder request, verbal description, market data, analytics report
  • Read every provided document thoroughly
  • If the user provides a verbal description only — proceed to Step 2 to structure it through discovery

Extract Raw Signals

From the provided inputs, extract and organize:

SignalSourceNotes
Problem[what pain exists, for whom][evidence or assumption]
Opportunity[what business value][data points]
User segments[who needs this][ICP/persona indicators]
Competitive context[how others solve it][differentiation angle]
Constraints[timeline, budget, technical, regulatory][hard vs soft]
Existing assets[related features, prior art, dependencies][links/refs]

If critical signals are missing (no clear problem statement, no target user) — ask before proceeding. Do not invent user needs.

2. Discovery and Framing

2a. Problem Validation

Define the problem with precision:

  1. Problem statement: One paragraph — who has the problem, what the problem is, why it matters now
  2. Evidence: Data points supporting the problem (usage metrics, support volume, churn correlation, user quotes, competitive pressure)
  3. Impact of inaction: What happens if we do nothing

If evidence is weak — flag this as a risk. Do not fabricate data.

2b. Target Users

Apply JTBD and ICP frameworks from Agent(product-manager):

  • Job-to-be-Done: When [situation], I want to [motivation], so I can [outcome]
  • ICP segments: Which customer profiles benefit most. Include triggers, buying signals, objections
  • Personas (if useful): Name, role, goal, frustration. Keep lightweight — max 2 personas

2c. Scope Decision

Based on complexity, decide the deliverable type:

ComplexitySignalsDeliverable
SmallSingle service, < 1 week effort, clear solutionFeature Brief (abbreviated PRD)
MediumMulti-component, 1–4 weeks, some unknownsFull PRD
LargeMulti-service, 4+ weeks, significant unknowns, new capabilitiesFull PRD + Spike/Discovery tasks
AI/AgentLLM-powered, autonomous behavior, trust/safety concernsFull PRD + Agent Contract + Eval Strategy

Present the scope decision to the user for confirmation before proceeding.

3. Requirements Definition

3a. Functional Requirements

List requirements prioritized using MoSCoW:

  • Must have: Core functionality — feature is useless without these
  • Should have: Important but not blocking launch
  • Could have: Nice-to-have, defer if constrained
  • Won't have (this iteration): Explicitly excluded — prevents scope creep

Each requirement: one sentence, testable, outcome-focused. Never specify implementation — describe what, not how.

3b. Non-Functional Requirements

Identify relevant NFRs:

CategoryRequirementTarget
Performance[e.g., response time][e.g., < 200ms p95]
Security[e.g., auth, data protection][e.g., RBAC, PII encrypted]
Scalability[e.g., concurrent users][e.g., 10K concurrent]
Accessibility[e.g., WCAG level][e.g., WCAG 2.2 AA]
Compliance[e.g., GDPR, SOC2][specific requirements]

Only include categories relevant to this feature.

3c. Acceptance Criteria

Write acceptance criteria for every Must-have and Should-have requirement:

  • Use Given/When/Then format for behavioral criteria
  • Include happy path, edge cases, error states
  • Include operational criteria: "no new errors in logs", "latency < Xms p95"
  • Include security criteria: "unauthorized users receive 403", "PII not logged"
  • Each criterion is independently testable

4. Success Metrics

Define how to measure feature success:

4a. Metric Framework

Metric TypeMetricTargetMeasurement Method
Primary (North Star)[e.g., activation rate][target value][how to measure]
Leading[e.g., feature adoption D7][target value][how to measure]
Guardrail[e.g., error rate, latency][must not exceed][how to measure]

4b. Instrumentation Plan

  • Events to track (name, properties, trigger)
  • Dashboards to create or update
  • Alerts to configure (guardrail breaches)

5. Risk Assessment

RiskTypeImpactLikelihoodMitigation
[description]Technical / Business / Security / ComplianceHigh/Med/LowHigh/Med/Low[strategy]

Mandatory risk categories to evaluate:

  • Security threats (apply OWASP Top 10; add LLM Top 10 for AI features)
  • Data handling risks (PII, secrets, retention)
  • Backward compatibility and migration
  • Dependency on external systems or teams
  • User abuse scenarios

6. AI/Agent Addendum

Include this section only for AI-powered or agent features. Skip for standard features.

<agent_contract>

  • Autonomy level: Assist (human decides) → Semi-auto (agent proposes, human approves) → Auto (agent acts independently)
  • Allowed tools and permissions: Least privilege. List every tool/API the agent can access
  • Confirmation gates: Which actions require human approval
  • Failure modes: What happens when the agent fails, hallucinates, or exceeds scope
  • Cost budget: Token/compute/API limits per operation
  • Context pipeline: Consult context-engineering skill for context stack design, RAG pipeline, memory architecture, agent harness patterns, and production checklists
  • Eval strategy: Offline eval set (fixtures, synthetic + real cases), online monitoring (drift, failure rates) </agent_contract>

7. Compile Deliverable

Full PRD

Compile all sections into a structured PRD:

# PRD: [Feature Name]

## Problem Statement
[From Step 2a]

## Target Users
[From Step 2b — JTBD, ICP, personas]

## Scope and Non-Goals
[From Step 2c — what's in, what's explicitly out]

## Requirements
[From Step 3a — MoSCoW prioritized]

## Non-Functional Requirements
[From Step 3b]

## Acceptance Criteria
[From Step 3c]

## Success Metrics
[From Step 4]

## Risks and Mitigations
[From Step 5]

## Agent Contract
[From Step 6 — only for AI features]

## Rollout Strategy
- Phase 1: Internal / dogfood
- Phase 2: Beta (limited users, feature flag)
- Phase 3: GA (all users)
- Backward compatibility notes
- Feature flag name and config

Feature Brief (for small scope)

Abbreviated format — single document:

# Feature Brief: [Feature Name]

**Problem**: [1–2 sentences]
**Users**: [target segment]
**JTBD**: When [situation], I want to [motivation], so I can [outcome]

## Requirements
[Must-have list only — max 5 items]

## Acceptance Criteria
[Given/When/Then for each requirement]

## Success Metric
[Single primary metric + target]

## Risks
[Top 1–3 risks with mitigations]

Present the compiled deliverable to the user for review.

8. Multi-Reviewer Feedback Loop

The PRD or Feature Brief MUST pass a mandatory multi-reviewer cycle before handoff. Do not update FEATURES.md or hand off to the architecture skill / plan skill until every reviewer returns approved.

Reviewer Panel

Apply each role below in sequence, treating each as an independent reviewer with its own pass over the deliverable:

  • product-manager role — problem framing, scope, requirements clarity, acceptance criteria testability, success metrics, risk coverage
  • marketing-strategist role — positioning, target audience alignment, messaging, GTM fit, competitive differentiation
  • content-writer role — structure, terminology consistency, clarity, readability
  • seo-engineer role — feature naming searchability, keyword alignment, AI citability (GEO/AEO), discoverability hooks for public-facing surfaces

Cycle

  1. For each role, produce a findings report: Critical (must fix), Major (should fix, justify if waived), Minor (optional), plus an explicit verdict: approved / approved-with-changes / rejected. Keep reports separate per role
  2. Collect all four reports before editing
  3. Apply all actionable findings. Resolve conflicts with priority Critical > Major > Minor; on ties, product-manager > content-writer > marketing-strategist > seo-engineer. Record waivers with a one-line rationale
  4. Re-run the same four reviewer passes against the updated deliverable
  5. Loop until every reviewer returns approved with zero remaining critical/major findings

Termination: pass when all four are approved. On divergence (findings not shrinking, mutually exclusive asks) — pause and ask the user to arbitrate. Max 5 cycles before escalation.

Record the review history at the bottom of the deliverable as a ## Review History section listing each cycle's reviewer verdicts and open issue counts.

9. Update FEATURES.md

After the PRD/brief is approved:

  1. If FEATURES.md does not exist — create it at the project root
  2. Add or update the feature entry:
    • Name, one-line description
    • Status: planned
    • Link to PRD/brief in features/ directory
  3. Save the PRD/brief to features/[feature-name].md (kebab-case)

10. Handoff

Guide the next step based on feature complexity:

ComplexityNext Step
Small (brief)Run plan skill directly — architecture is implicit
Medium (PRD)Run architecture skill for technical design, then plan skill
Large (PRD + spikes)Execute spikes first, then architecture skill → plan skill
AI/Agent (PRD + contract)Run architecture skill with agent contract as input → plan skill

Integration

  • Input: Raw feature resources (ideas, research, feedback, stakeholder requests)
  • Followed by: architecture skill (technical design), plan skill (work decomposition)
  • Roles: product-manager role (primary — owns PRD), marketing-strategist + content-writer + seo-engineer roles (Step 8 reviewers), solution-architect role (consulted for feasibility)
  • Skills: context-engineering skill (context pipeline design, RAG, memory, agent harness — for AI/Agent features, Step 6)
  • Updates: FEATURES.md, features/ directory
  • Enables: Full planning chain: product skill → architecture skill → plan skill → feature-dev skill

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.