Ngenaire Docs
Log inSign up free

Prompting guide

The AI Assistant is most effective when you give it context, are specific about the deliverable, and work in multiple turns. This page collects practical habits and example prompts you can adapt.

Habits that produce good results

  • Give it context. Name the artifact or scope you mean — a requirement code (REQ-014), a CONOPS section, a specific phase. "The authentication requirement" might match several; an exact id never does.
  • Be specific about the deliverable. Say what you want and what shape it should take: the method to use, the audience, a length bound, or the columns of a table.
  • Work in multiple turns. A first draft is rarely the final draft. Reply with corrections — the assistant continues the conversation and refines its work.
  • Let it use Project Memory. Durable facts you have saved to Project Memory are read automatically, so decisions and constraints carry forward without repeating them. If something is missing, ask the assistant to remember it.
  • Split unrelated asks. Bundling two unrelated tasks into one prompt produces shallow output. One job per prompt works better.
  • Use a specialist for focused work. When you know the role, launch a specialist sub-agent so the assistant applies that role's conventions.

Example prompts

Requirements drafting

Convert this paragraph into EARS-format requirements:
"Users should be able to reset their password and the system should email them a reset link within one minute."

Decompose REQ-007 into three children that are individually testable, and propose ids.

Draft functional requirements for the telemetry subsystem based on CONOPS section 3.

Quality auditing

Audit the requirement set for ambiguous wording. List each flagged requirement and explain the issue.

Find compound requirements that bundle more than one obligation and rewrite the worst offenders.

Check the requirement set for duplicates and near-duplicates and group them.

Test and RVTM work

For each requirement without a linked verification, propose one and choose a method (Test / Inspection / Analysis / Demonstration).

Draft a test case for REQ-031 with its scenario, expected results, and pass/fail criteria.

Audit the RVTM and summarize verification coverage for the safety-critical requirements as a one-paragraph brief for a TRR.

Risk

Identify the top five risks on this project by score and propose a mitigation for each.

Score residual risk for the open mitigations and recommend which to accept and which need further action.

Suggest risks implied by the current requirement set that are not yet in the register.

Schedule

Identify tasks at risk of slipping and propose recovery actions.

Summarize the current critical path and explain why each task is on it.

Recommend a re-baseline strategy if we slip by 10 working days.

Report generation

Generate a one-page status brief covering requirements progress, verification coverage, top risks, and the critical path. Audience: executive sponsor.

Draft an executive summary for an upcoming PDR, no more than 200 words.

Summarize what changed in this project over the last two weeks for a stakeholder update.

Before changes are applied

When a request implies multiple creates or any delete, the assistant describes its plan in plain English and asks you to confirm before it proceeds. You can always ask it to show you the change first.

Related