pm-clarify

Identify underspecified areas in project specifications and generate targeted clarification questions.

3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ArkLabsHQ/arkadian --skill pm-clarify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-clarify
Source: https://github.com/ArkLabsHQ/arkadian/tree/main/skills/pm-clarify
Command: npx skills add https://github.com/ArkLabsHQ/arkadian --skill pm-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses ambiguities and missing information within project specifications, ensuring all requirements are clearly defined before implementation begins.

Core Features & Use Cases

  • Identify Ambiguities: Pinpoints sections of a spec that lack detail or contain unclear instructions.
  • Targeted Questioning: Generates specific questions to elicit necessary clarification from stakeholders.
  • Use Case: When a feature requirement is vague (e.g., "improve user experience"), this skill helps the project manager ask precisely what aspects of the user experience need improvement and how success will be measured.

Quick Start

Ask the project manager to clarify the requirements for the new user authentication module.

Frequently Asked Questions about pm-clarify

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

FAQPage Schema
How do I identify ambiguities in project specifications?

The best way to clarify vague requirements is by generating specific, targeted questions for stakeholders. This ensures that underspecified features, such as a general request to improve user experience, are broken down into measurable and detailed instructions.

How do I generate targeted clarification questions for stakeholders?

You can generate targeted clarification questions for stakeholders by running a dedicated interactive clarification command that analyzes your project specifications and automatically prompts you with precise questions to gather missing information.

When do I need to clarify underspecified specs in a project?

You need to clarify underspecified specs when a feature requirement lacks detail or contains unclear instructions, ensuring all project requirements are clearly defined and validated before the implementation phase begins.

Does this clarification process work for any project management workflow?

Yes, this clarification process applies to project management workflows requiring detailed requirement gathering and validation, specifically utilizing a dedicated interactive command to conduct clarification sessions with stakeholders.