agentsclimarketplace

Requirement elicitation

Skill planifest/planifest-framework/planifest-framework/external-skills/requirement-elicitation

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill requirement-elicitation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Requirement elicitation workflow for collecting, reconciling, and structuring evidence before requirement baseline writing. Use when requirement inputs are incomplete and teams need high-confidence evidence gathering; do not use for final canonical requirement synthesis.

SKILL.md

1.9 KB, as published. Nobody here has run it

Requirement Elicitation

Overview

Use this skill to collect requirement evidence with traceability, confidence, and contradiction visibility.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Evidence strength rules:
    • references/evidence-strength-rules.md

Templates And Assets

  • Evidence intake template:
    • assets/evidence-intake-template.csv
  • Clarification question log:
    • assets/clarification-question-log-template.md

Inputs To Gather

  • Stakeholder map and decision owners.
  • Existing docs/tickets/incidents/analytics.
  • Known unknowns and contested assumptions.

Deliverables

  • Structured evidence set with confidence scores.
  • Clarification question backlog with owners.
  • Requirement candidate seeds for baseline synthesis.

Workflow

  1. Capture evidence in assets/evidence-intake-template.csv.
  2. Apply confidence/contradiction rules from references/evidence-strength-rules.md.
  3. Separate evidence, assumptions, and unknowns.
  4. Track unresolved questions in assets/clarification-question-log-template.md.
  5. Publish elicitation package for requirements-definition.

Quality Standard

  • Evidence has source traceability and confidence labels.
  • Contradictions are explicit and unresolved items are owned.
  • Inputs are sufficient for canonical baseline synthesis.

Failure Conditions

  • Stop when evidence depends on weak single-source claims.
  • Stop when critical unknowns have no owner/due date.
  • Escalate when legal/privacy constraints are unclear.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.