requirements-elicitation

v1.2.0

Analyse PRDs and feature specs for gaps, generate clarifying questions for PMs and engineers, and assess technical risk before implementation

CodexClaude Code1 Skill

By Wagner Ignacio Pinto JuniorLicense: MIT0 GitHub starsUpdated 4 days ago

Directory evidence

Runtimes: Codex and Claude Code
Parsed components: 1 skill or MCP entry
Source updated: Sep 19, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install requirements-elicitation for Codex and Claude Code

Installs for the current user

codex plugin marketplace add wagneripjr/skills
codex plugin marketplace upgrade wagner-skills-marketplace
codex plugin add requirements-elicitation@wagner-skills-marketplace

Paste and run these commands in a terminal with Codex. They add and refresh the wagner-skills-marketplace catalog, then install this plugin.

Compatibility: the page URL and API slug “requirements-elicitation” remain stable.

Codex: requirements-elicitation@agent-plugin-marketplace → requirements-elicitation@wagner-skills-marketplace

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/wagneripjr/skills

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/requirements-elicitation/.

Plugin files

plugins/requirements-elicitation/

├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
└── skills/requirements-elicitation/SKILL.md

Included Skills1

requirements-elicitationskills/requirements-elicitation/SKILL.md

Systematic framework for analyzing product documents (PRDs, feature specs, user stories, roadmaps, one-pagers) to identify gaps, generate clarifying questions for PMs and engineers, and assess technical risks. This skill should be used when engineers or technical leads need to bridge PM documents and implementation by eliciting missing technical details rather than making assumptions. Use when asked to extract technical requirements, review specs, identify what's missing, or prepare clarifying questions from product documents.

Plugin manifests2

plugins/requirements-elicitation/.codex-plugin/plugin.json

{
  "name": "requirements-elicitation",
  "description": "Analyse PRDs and feature specs for gaps, generate clarifying questions for PMs and engineers, and assess technical risk before implementation",
  "version": "1.2.0",
  "author": {
    "name": "Wagner Ignacio Pinto Junior",
    "email": "[email protected]"
  },
  "repository": "https://github.com/wagneripjr/skills",
  "homepage": "https://github.com/wagneripjr/skills",
  "license": "MIT",
  "keywords": [
    "requirements",
    "product",
    "elicitation"
  ],
  "skills": [
    "./skills/requirements-elicitation"
  ]
}

plugins/requirements-elicitation/.claude-plugin/plugin.json

{
  "name": "requirements-elicitation",
  "description": "Analyse PRDs and feature specs for gaps, generate clarifying questions for PMs and engineers, and assess technical risk before implementation",
  "version": "1.2.0",
  "author": {
    "name": "Wagner Ignacio Pinto Junior",
    "email": "[email protected]"
  },
  "repository": "https://github.com/wagneripjr/skills",
  "homepage": "https://github.com/wagneripjr/skills",
  "license": "MIT",
  "keywords": [
    "requirements",
    "product",
    "elicitation"
  ]
}