omp packages

@firstpick/pi-skill-requirements-engineering0.1.0

Portable Agent Skill for starting, updating, and resuming evidence-based requirements engineering with traceable records and human approval boundaries.

firstpick Published 1 month ago MIT ~131 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Did it work for you?

Result

One report per person. A new report replaces your old one.

Reports 0

No reports yet.

Readme

Requirements engineering

Start, update, or resume software requirements work without turning guesses into stakeholder decisions.

Helpful when

  • You have an early project idea and need the next useful requirements step.
  • Existing plans, documents, and code disagree about what the project should do.
  • A requirement changed and you need to see the effect on records, checks, and planned work.
  • You need a draft interview guide, survey, workshop agenda, observation sheet, or review checklist.

What to share with Pi

  • The project directory and whether you want to start, update, or resume the work
  • Any plan you may want to continue, plus current requirements, decisions, status notes, or tracker links
  • The business problem, relevant stakeholder roles, approval process, privacy limits, and preferred language when known
  • The working document you need and who will use it

You can begin with only a project directory. Pi will first show candidate continuation plans and ask before using one. If you choose none, it will inspect a small amount of project evidence and give you either a revisable plan or a concrete next-step guide.

Try asking

Resume the requirements work in this project. Show me the candidate plans before choosing one, separate confirmed facts from code-based inferences, and prepare the next interview guide if stakeholder input is the blocker.

Other useful requests include:

Start requirements engineering for this project. I only know that volunteers struggle to schedule shifts.

REQ-17 may need to change. Show the impact before editing any approved requirement.

What you'll get

  • A maintained requirements-engineering plan or a guide to the next safe step
  • Traceable requirements, decisions, unknowns, and stakeholder confirmation gaps
  • Draft working documents tied to a stated purpose and source
  • A change preview that identifies stale reviews and affected checks before agreed material changes

Keep in mind

Pi can organize evidence and draft questions, but it cannot interview absent people, approve requirements, authorize implementation, or prove that software was delivered. Review drafts and get confirmation from the people who hold that authority.

Requirements records and interview notes may contain personal or commercially sensitive information. Choose a storage location and retention policy before saving them. The skill never contacts stakeholders or sends surveys for you.

Install

pi install npm:@firstpick/pi-skill-requirements-engineering

After installation, restart Pi if the skill does not appear in your current session.

Technical details

See TECHNICAL.md for advanced usage, compatibility, privacy, and limitations.