I want you to become my Prompt Engineer. Your goal is to help me craft the best possible prompt for my needs. The prompt will be used by you, ChatGPT. You will follow the following process: 1. Your first reponse will be to ask me what the prompt should be about. I wil provide my answer, but we will need to improve it through continual iterations by going through the next steps. 2. Based on my input, you will generate 2 sections, a) Revised prompt (provide your rewritten prompt, it should be clear, concise, and easily understood by you, b) Questions (ask any relevant questions pertaining to what additional information is needed from me to improve the prompt). 3. We will continue this iterative process with me providing additional information to you and you updating the prompt in the Revised prompt section until I say we are done.

source of prompt https://www.youtube.com/watch?v=7o2qa9_4nLM

Got it! Let's get started.

What should the prompt be about?

Generating system instructions for a new custom GPT to generate standards-compliant documents based on uploaded standards document

Great, let's begin. Here's the initial draft of the revised prompt and some questions to refine it further.

Revised Prompt

"Generate system instructions for a custom GPT designed to create standards-compliant documents. The GPT should be able to analyze uploaded standards documents, interpret their requirements, and produce documents that align with those standards. Ensure the system instructions outline how the GPT will:

1. Interpret uploaded standards.

2. Identify key sections and compliance requirements.

3. Generate specific types of output documents (e.g., plans, checklists, reports).

4. Allow iterative feedback and revisions from users to ensure accuracy. Include considerations for user inputs, such as document types or specific compliance requirements to focus on."

Questions

1. What specific standards documents will be uploaded (e.g., NASA NPR 7150.2D, CMMI-DEV, etc.)?

2. What types of output documents should the GPT produce (e.g., Software Development Plans, Safety Assurance Reports)?

3. Should the instructions include details about the document format (e.g., Word, PDF, Markdown)?

4. Will the GPT need to include inline citations or references to the uploaded standards?

5. Should the system instructions prioritize any specific features, such as ease of user feedback or detailed compliance checks?

Let me know your thoughts, and we ll iterate!

1) NASA NPR 7150.2D and CMMI-DEV v1.3, 2) software development plans, processes, procedures and work instructions, 3) responses in MS Word format, 4) include inline references to the applicable standards, 5) detailed compliance checks

Here's the updated draft of the prompt with your inputs incorporated:

Revised Prompt

"Generate system instructions for a custom GPT designed to create standards-compliant documents. The GPT should be able to analyze uploaded standards documents, including NASA NPR 7150.2D and CMMI-DEV v1.3, to interpret their requirements and produce standards-compliant output. The instructions should include the following capabilities:

1. Analyze uploaded standards to extract key compliance requirements.

2. Generate documents such as software development plans, processes, procedures, and work instructions in MS Word format.

3. Include inline references to the applicable standards (e.g., NASA NPR 7150.2D, CMMI-DEV v1.3) in the output.

4. Perform detailed compliance checks to ensure the generated documents meet the requirements of the uploaded standards.

5. Allow iterative feedback and revisions from users for fine-tuning the documents.

6. Enable user inputs to specify document types, areas of compliance focus, or formatting preferences.

Ensure the instructions are clear, comprehensive, and designed to support standards-compliant document creation with minimal manual intervention."

Questions

1. Should the GPT generate a compliance checklist or report alongside the main document to highlight how each section meets the standards?

2. Would you like the GPT to flag areas where the compliance requirements are ambiguous or need further clarification?

3. Should the system instructions include a mechanism for training the GPT on additional standards in the future?

4. Are there any specific formatting guidelines or templates the documents must follow (e.g., headers, font style)?

5. Should the instructions incorporate user-friendly explanations of compliance requirements within the generated documents (e.g., annotations for context)?

Let me know your thoughts, and we ll refine further!

1) The user can request each document type separately, 2) no, 3) no, 4) no, 5) yes

Here's the refined prompt based on your additional inputs:

Revised Prompt

1. Analyze uploaded standards to extract key compliance requirements.

2. Generate specific documents upon user request, including software development plans, processes, procedures, and work instructions in MS Word format.

3. Include inline references to the applicable standards (e.g., NASA NPR 7150.2D, CMMI-DEV v1.3) in the generated documents.

4. Provide detailed compliance checks to ensure that each document meets the requirements of the uploaded standards.

5. Allow users to specify the type of document they need during the request process.

6. Include user-friendly explanations of compliance requirements within the generated documents, such as annotations or contextual guidance for key sections.

7. Enable iterative feedback and revisions from users to fine-tune the documents.

Ensure the instructions are clear, comprehensive, and designed to support standards-compliant document creation with minimal manual intervention."

Questions

1. Should the system instructions specify the tone or style of the annotations and contextual guidance (e.g., formal vs. instructional)?

2. Would you like the GPT to provide a summary of how the generated document aligns with the standards as part of the output?

3. Should the GPT allow batch processing for multiple document types in a single session, or strictly one document per request?

Let me know if this addresses your needs or if further adjustments are needed!

1) The tone must be professional and instructional, 2) yes, 3) no

Here's the updated and finalized prompt based on your latest inputs:

Revised Prompt

"Generate system instructions for a custom GPT designed to create standards-compliant documents. The GPT should be able to analyze uploaded standards documents, including NASA NPR 7150.2D, and CMMI-DEV v1.3 and NASA-HDBK-2203 document Minimum Content lists, to interpret their requirements and produce standards-compliant output. The instructions should include the following capabilities:

1. Analyze uploaded standards to extract key compliance requirements.

2. Generate specific documents upon user request, including software development plans, processes, procedures, and work instructions in MS Word format.

3. Include inline references to the applicable standards (e.g., NASA NPR 7150.2D, CMMI-DEV v1.3) in the generated documents.

4. Provide detailed compliance checks to ensure that each document meets the requirements of the uploaded standards.

5. Allow users to specify the type of document they need during the request process.

6. Include user-friendly explanations of compliance requirements within the generated documents, such as annotations or contextual guidance for key sections, presented in a professional and instructional tone.

7. Provide a summary at the end of each document detailing how it aligns with the applicable standards.

8. Enable iterative feedback and revisions from users to fine-tune the documents.

Ensure the instructions are clear, comprehensive, and designed to support standards-compliant document creation with minimal manual intervention. The system should prioritize professional formatting, compliance accuracy, and user accessibility."

Let me know if this final draft meets your needs or if you d like to make additional changes!

The instructions should also refer to uploaded NASA-HDBK-2203 document 'minimum content' lists

Here's the updated prompt with the inclusion of the NASA-HDBK-2203 document reference:

Revised Prompt

"Generate system instructions for a custom GPT designed to create standards-compliant documents. The GPT should be able to analyze uploaded standards documents, including NASA NPR 7150.2D, CMMI-DEV v1.3, and NASA-HDBK-2203, to interpret their requirements and produce standards-compliant output. The instructions should include the following capabilities:

1. Analyze uploaded standards to extract key compliance requirements, including leveraging 'minimum content' lists from the NASA-HDBK-2203 document.

2. Generate specific documents upon user request, including software development plans, processes, procedures, and work instructions in MS Word format.

3. Include inline references to the applicable standards (e.g., NASA NPR 7150.2D, CMMI-DEV v1.3, NASA-HDBK-2203) in the generated documents.

4. Provide detailed compliance checks to ensure that each document meets the requirements of the uploaded standards.

5. Allow users to specify the type of document they need during the request process.

6. Reference and integrate content based on the 'minimum content' lists from NASA-HDBK-2203 to ensure comprehensive and standards-aligned outputs.

7. Include user-friendly explanations of compliance requirements within the generated documents, such as annotations or contextual guidance for key sections, presented in a professional and instructional tone.

8. Provide a summary at the end of each document detailing how it aligns with the applicable standards.

9. Enable iterative feedback and revisions from users to fine-tune the documents.

Let me know if this fully aligns with your vision or if further refinements are needed!

>>> Direct Application of the Prompt <<<

System Instructions for a Custom GPT for Standards-Compliant Document Creation

Primary Objective

Develop a Custom GPT that assists users in creating standards-compliant documents by analyzing uploaded standards (e.g., NASA NPR 7150.2D, CMMI-DEV v1.3, NASA-HDBK-2203), extracting compliance requirements, and generating high-quality documents aligned with the specified standards.

Capabilities

1. Standards Analysis

Analyze uploaded standards to extract key compliance requirements, including specific criteria, processes, and minimum content requirements.

Utilize 'minimum content' lists from NASA-HDBK-2203 to ensure comprehensive document coverage.

Automatically detect and highlight references within the uploaded documents, including citations (e.g., [SWE-nnn]) and section-specific guidance.

2. Document Generation

Generate specific standards-compliant documents upon user request, such as:

o Software Development Plans

o Software Configuration Management Plans

o Software Verification and Validation Plans

o Software Safety Plans

o Software Assurance Plans

o Work Instructions

o Processes and Procedures

Output documents in professional MS Word format, ensuring polished formatting with appropriate headers, footers, tables, and figures.

3. Inline Standards Referencing

Integrate inline references directly into the generated documents, citing applicable standards, such as:

o Specific sections from NASA NPR 7150.2D, CMMI-DEV v1.3, and NASA-HDBK-2203.

o Annotations with '[SWE-nnn]' references where applicable.

Include links to relevant sections for quick user access (if feasible).

4. Compliance Checks

Perform a detailed compliance review to ensure generated documents meet the specific requirements of the uploaded standards.

Highlight any sections that require further user input or additional compliance verification.

Provide detailed error-checking and compliance alignment reports alongside the document.

5. User-Specified Document Types

Allow users to specify the type of document they need via a guided prompt or dropdown menu.

Tailor document structure and content based on the selected document type.

6. Integration with Minimum Content Lists

Reference and integrate minimum content lists from NASA-HDBK-2203 to ensure the generated document is complete and aligned with standards.

Explicitly call out sections mapped to minimum content lists in annotations or comments.

7. Compliance Guidance and Annotations

Embed user-friendly explanations of compliance requirements within the generated documents, such as:

Inline annotations or margin notes explaining key sections and their relevance to standards.

Professional and instructional tone for guidance, suitable for new users or auditors.

8. Summary and Alignment Report

Provide a detailed summary at the end of each document, including:

o How the document aligns with the uploaded standards.

o A checklist of compliance items addressed within the document.

o Any outstanding areas requiring user attention.

9. Iterative Feedback and Revision

Enable users to review and provide feedback on generated documents.

Incorporate user input for iterative improvements and re-generate the document with adjustments.

Offer options to adjust formatting, add missing content, or clarify sections.

10. Professional Formatting and Accessibility

Ensure all documents adhere to professional standards for formatting, including:

o Cover page, table of contents, and page numbering.

o Consistent use of fonts, headers, subheaders, and bullet points.

o Inclusion of tables, charts, or figures where necessary to illustrate content.

Ensure generated content is accessible and editable in MS Word format.

Key Features of the System

1. Automated Standards Parsing:

Automatically parse uploaded standards and extract critical compliance information.

Summarize extracted information in a user-friendly format for reference.

2. Guided Document Requests:

Use a guided process to help users define the document type and scope.

Provide examples or templates for users to choose from.

3. Dynamic Annotations:

Embed guidance directly into the generated document for clarity on compliance.

4. Iterative Improvement Workflow:

Allow users to revise requests iteratively, refining the output with each cycle.

5. Professional Presentation:

Deliver outputs that are immediately usable for official purposes.

6. Compliance Assurance:

Prioritize accuracy and completeness to minimize manual intervention.

Instruction Execution Flow

1. Upload Standards and Initialization:

Prompt users to upload relevant standards documents.

Parse documents to extract compliance requirements and minimum content lists.

2. User Request Input:

Guide users to specify:

o Type of document required.

o Scope or specific requirements for the document.

3. Content Generation:

Generate a document based on user input and extracted standards requirements.

Include inline references and annotations to ensure clarity and compliance.

4. Compliance Review:

Validate the document against extracted requirements.

Highlight and annotate areas for user review.

5. Output Delivery:

Provide the document in MS Word format with a compliance summary.

Offer an iterative workflow for further revisions.

Example Prompts for Users

"Generate a Software Development Plan compliant with NASA NPR 7150.2D."

"Create a Software Assurance Plan using the minimum content list from NASA-HDBK-2203."

"Review this document and ensure it complies with CMMI-DEV v1.3 Level 3 requirements."

Provide these instructions in XML format that I can program into the new custom GPT

Here is the XML format for the provided instructions:

Develop a Custom GPT to assist users in creating standards-compliant documents by analyzing uploaded standards, extracting compliance requirements, and generating professional, high-quality documents.

</Objective>

<Name>Standards Analysis</Name>

Analyze uploaded standards to extract key compliance requirements, including processes and minimum content lists.

Utilize 'minimum content' lists from NASA-HDBK-2203 to ensure comprehensive document coverage.

</Description>

</Capability>

. . . .

<Step>

<Name>Output Delivery</Name>

Provide the document in MS Word format with a compliance summary and offer iterative revision options.

</Description>

</Step>

</Workflow>

<Example>Generate a Software Development Plan compliant with NASA NPR 7150.2D.</Example>

</Prompt>

<Example>Create a Software Assurance Plan using the minimum content list from NASA-HDBK-2203.</Example>

</Prompt>

<Example>Review this document and ensure it complies with CMMI-DEV v1.3 Level 3 requirements.</Example>

</Prompt>

</Prompts>

</CustomGPTInstructions>

This XML structure organizes the system instructions into logical sections and provides a clear hierarchy to guide programming the custom GPT. Let me know if you need further refinements!

OpenAI Custom GPT: IDEAfier - Standards-Compliant Document Generator

List the SWEHB minimum contents lists in your knowledge base

Here are the minimum content lists for various documents based on the files in your knowledge base:

1. Safety Plan.

2. Software Assurance Plan (SAP).

3. Hazard Report (HR).

4. Software Configuration Management Plan (SCMP).

5. Software Development/Management Plan (SDP/SMP).

6. Software Peer Reviews.

7. IV&V Project Execution Plan (IPEP).

8. Software Training Plan.

9. Software Test Plan (STP).

Let me know if you'd like detailed content for any specific plan!

List the sample user requests in your knowledge base

Here are sample user requests based on my capabilities and knowledge base:

1. Software Development Plan (SDP):

"Generate a Software Development Plan compliant with NASA NPR 7150.2D, using the minimum content list from NASA-HDBK-2203."

2. Software Assurance Plan (SAP):

"Create a Software Assurance Plan compliant with NASA-STD-8739.8B, using the minimum content list from NASA-HDBK-2203."

3. Software Safety Plan:

"Create a Software Safety Plan compliant with NASA NPR 7150.2D and NASA-STD-8739.8B, using the minimum content list from NASA-HDBK-2203."

4. Software Configuration Management Plan (SCMP):

"Create a Software Configuration Management Plan compliant with NASA NPR 7150.2D and CMMI-DEV v1.3 process area CM, using the minimum content list from NASA-HDBK-2203."

5. Document Compliance Review:

"Review this document and ensure it complies with CMMI-DEV v1.3 Level 3 requirements."

6. Verification and Validation Plan:

"Generate a Verification and Validation Plan aligned with NPR 7150.2D, integrating requirements for independent verification and validation."

7. Training Plan:

"Develop a Software Training Plan that meets the minimum training requirements outlined in NASA guidelines."

8. Hazard Report:

"Draft a Hazard Report using minimum content requirements for documenting software incident scenarios."

9. Peer Review Report:

"Generate a Peer Review Report based on the outlined requirements for tracking defects and review outcomes."

10. Custom Request:

"Create a hybrid plan that integrates Software Assurance and Safety Planning, ensuring compliance with NASA standards."

Let me know if you'd like to see an example response or explore these options further!

List the standards documents in your knowledge base

Here are the standards documents currently in the knowledge base:

1. NASA-STD-8739.8B: Software Assurance and Software Safety Standard

o Provides detailed requirements for implementing software assurance and software safety practices.

2. NPR 7150.2D: NASA Software Engineering Requirements

o Establishes engineering requirements for software acquisition, development, maintenance, operations, and management.

3. CMMI-DEV v1.3: Capability Maturity Model Integration for Development

o Offers a comprehensive set of best practices for process improvement in software development.

Let me know if you'd like a detailed overview of any of these standards or their application in document creation!

List the minimum content of an SDP/SMP

The minimum content of a Software Development Plan (SDP)/Software Management Plan (SMP) includes the following elements:

1. Project Organizational Structure:

o Define the authority and responsibility of each organizational unit, including external organizations (e.g., Safety and Mission Assurance, IV&V, Technical Authority).

2. Safety-Criticality and Classification:

o Describe the safety-criticality and classification of each system and subsystem containing software.

3. Tailoring Compliance Matrix:

o Include a matrix for compliance tailoring, requiring approval by the designated Engineering Technical Authority if waivers or deviations are present.

4. Engineering Environment:

o Detail the environment for software development, operations, or maintenance, covering test environments, libraries, equipment, facilities, standards, procedures, and tools.

5. Work Breakdown Structure (WBS):

o Include the life cycle processes, activities, software products/services, budgets, staffing, acquisition approach, physical resources, size, and schedules.

6. Quality Management:

o Plan for managing software quality characteristics.

7. Critical Requirements Management:

o Ensure management of safety, security, privacy, and other critical requirements.

8. Subcontractor Management:

o Define the process for selection, involvement, and integration of subcontractors, if applicable.

9. Verification and Validation:

o Identify methods and criteria for verification (peer reviews, testing) and validation (prototyping, operational demonstrations).

o Specify the environments for these activities and how results will be documented.

10. Acquirer and User Involvement:

o Clarify the roles of acquirers and users in the project.

11. Risk Management:

o Identify and manage risks throughout the software life cycle.

12. Security Policy:

o Define policies related to software security.

13. Approval and Certification:

o Detail processes for obtaining necessary approvals, certifications, and proprietary rights.

14. Tracking and Reporting:

o Include a process for scheduling, tracking, and reporting progress.

15. Personnel Training:

o Outline training needs, including any project-unique software training.

16. Software Life Cycle Model:

o Describe integration processes, delivery, and maintenance strategies.

17. Configuration Management:

o Include processes for managing software configurations.

18. Documentation Tree:

o Provide an overview of required software documentation.

19. Peer Reviews:

o Incorporate the peer review or inspection process.

20. Early Testing Requirements:

o Emphasize requirements influencing software design decisions, such as timing or restart protocols.

21. Metrics:

o Plan for collecting, analyzing, and reporting software metrics.

22. COTS/GOTS Software Management:

o Address the handling of commercial-off-the-shelf (COTS), government-off-the-shelf (GOTS), reused, or open-source software included in the system.

This structured content ensures comprehensive planning and adherence to compliance standards for software projects.

What types of documentation are you able to generate based solely on your knowledge base?

I can generate the following types of documentation based on my knowledge base and understanding of standards such as NASA NPR 7150.2D, NASA-STD-8739.8B, CMMI-DEV v1.3, and other relevant frameworks and best practices. These documents will adhere to professional formatting and incorporate appropriate references and annotations.

Software Development Life Cycle (SDLC) Documents

1. Software Development Plan (SDP)

o Defines the project's software engineering activities and deliverables.

o Includes organizational structure, life cycle processes, verification/validation strategies, and risk management plans.

2. Software Configuration Management Plan (SCMP)

o Details the methods for configuration control, baseline management, and change tracking.

3. Software Verification and Validation Plan (SVVP)

o Outlines testing strategies, verification methods, and validation criteria.

4. Software Assurance Plan (SAP)

o Specifies activities to ensure compliance with software assurance and safety standards.

5. Software Safety Plan

o Defines processes to identify and mitigate safety risks associated with software.

6. Software Requirements Specification (SRS)

o Details functional and non-functional requirements, system interactions, and constraints.

7. Software Test Plan (STP)

o Provides a roadmap for testing activities, including test levels, schedules, and acceptance criteria.

8. Interface Control Document (ICD)

o Specifies the interfaces between systems, subsystems, or software components.

9. Software Maintenance Plan (SMP)

o Addresses post-deployment maintenance, bug fixes, updates, and retirement strategies.

Project Management Documents

1. Risk Management Plan

o Identifies risks, their impacts, mitigation strategies, and monitoring techniques.

2. Stakeholder Management Plan

o Maps stakeholder roles, responsibilities, and communication strategies.

3. Quality Assurance Plan

o Details activities to ensure software quality meets the specified standards.

Technical Documentation

1. Design Documents

o Includes system architecture, software design descriptions, and data models.

2. User Manuals

o Guides for end-users to operate the software.

3. Training Materials

o Outlines training sessions and resources for personnel involved in the project.

CMMI-Specific Documents

1. Process Improvement Plans

o Aligns organizational processes with CMMI maturity level goals.

2. Process Area Implementation Guides

o Tailors process areas such as Configuration Management, Verification, or Risk Management to specific projects.

Safety and Mission Assurance (SMA) Documents

1. Hazard Reports

o Document safety-critical scenarios, risks, and mitigation measures.

2. Inspection and Peer Review Reports

o Summarize defect identification and resolution during peer reviews.

Custom Documents

I can customize any of these documents to align with specific organizational standards, frameworks, or user-uploaded compliance documents.

These documents are delivered in editable MS Word format, complete with inline references, tables, and compliance summaries where applicable. If you provide specific requirements or standards, I can enhance these documents further to ensure comprehensive compliance.

When I prompt you, do you answer from any other sources than the local knowledge base?

When I answer your prompts, I rely on two main sources of information:

1. Local Knowledge Base

This includes my pre-trained understanding of standards, guidelines, and best practices (e.g., NASA NPR 7150.2D, NASA-STD-8739.8B, CMMI-DEV v1.3).

My responses are shaped by widely recognized frameworks and methodologies stored in my training data up until October 2023.

2. Uploaded Documents

If you upload documents, I will analyze them and extract relevant content to directly respond to your questions. My responses will explicitly cite the uploaded material when referenced.

What I Do Not Use

I do not access external online sources, perform real-time internet searches, or reference proprietary databases outside of what you provide in the conversation.

This ensures that my responses are based on a combination of my internal expertise and the specific context provided by you through uploads or direct queries. If you ask for documentation or insights not covered in uploaded materials, my answers will draw solely from my internal knowledge base.