Skip to content
v1.4.1

Connect ChatGPT or Codex to DDNA and do anything Project Chat can: requirements, Project Intent, the engineering model and bill of materials, change control, technical reviews, DFMEA, deliverables, tasks, gates, and stand-ups, using your own DDNA account and permissions.

ddna-change-control

Work with DDNA change control and technical reviews. Covers engineering change proposals, deviations and waivers, the change board, what a release still needs a proposal for, and technical reviews with their criteria and action items. Use when the user asks to raise, edit, submit, or withdraw a change proposal, deviation, or waiver, or to plan, convene, or track a technical review.

ddna-deliverables

Work with a DDNA project's deliverable documents. Covers the system/subsystem specification, interface control document, verification cross-reference matrix, and architecture views description, plus their Word exports, review decisions, document control settings, and release readiness. Use when the user asks to open, check, export, or review a deliverable, or asks whether the deliverables are ready for a release. Not for releasing a baseline or building a release package (ddna-engineering), or for change proposals (ddna-change-control).

ddna-dfmea

Work with a DDNA project's design failure mode and effects analysis (DFMEA). Covers the project summary, analyses and their worksheets, runs, evidence questions, failure chain corrections, the milestone policy, and exports. Use when the user asks about failure modes, causes, effects, controls, or ratings, or asks to answer a DFMEA question, correct a failure chain, or start or check a DFMEA run. Not for program risks, assumptions, or requirement findings (ddna-requirement-ide).

ddna-engineering

Work on a DDNA project's engineering model. Covers configurations, the System map and its notes, parts, boards, the bill of materials, budgets, requirement coverage and allocation, imports from Onshape and other files, subsystem projects, baselines and releases, change impact, engineering issues, the project's Git record, and release packages. Use when the user asks to read, change, import into, or release the engineering model or its bill of materials. Not for Intent documents (ddna-intent), change proposals or technical reviews (ddna-change-control), deliverable documents (ddna-deliverables), or tasks (ddna-tasks).

ddna-intent

Work on a DDNA project's Intent. Covers the Intent questions and interview, the Intent documents and their revisions, tracked edits, comments, guidance notes, registers such as hazards, constraints, and readiness evidence, visuals, trade studies, generation runs, and review and approval. Use when the user asks to answer Intent questions, read or edit an Intent document or register, generate or update Intent, or review, approve, or return one. Not for requirements and their approval (ddna-requirement-ide) or deliverable documents (ddna-deliverables).

ddna-making-changes

The rules for changing a DDNA project from an assistant. Covers when to save a proposal and when to change a record directly, the project_version check, safe retries, generation runs, download links, permissions, and refusals. Use before the first change in a conversation, and whenever DDNA refuses a change or says the project changed.

ddna-project-admin

Set up and administer a DDNA project. Covers project details and status, connected sources such as GitHub, Notion, and Google Drive, source files, evidence, the project team, invitations and access, and archiving or deleting a project. Use when the user asks to rename or archive a project, connect or sync a source, add evidence, or see or change who has access. Not for assigning tasks or setting who carries a task role (ddna-tasks).

ddna-project-knowledge

Get oriented in a DDNA project and find what it already records. Use when the user asks what a project is, where it stands, what is blocking it, what was decided, what changed since last time, or asks a question the project's saved facts could answer. Not for changing records; use the skill for the record being changed.

ddna-requirement-ide

Review, refine, write, and close out DDNA requirements, and work the findings, risks, assumptions, and guided questions around them. Use when the user asks to review a requirement for quality or testability, find what a requirement is missing, add or edit a requirement or its fields, record evidence or answers, approve or reject a requirement or a change proposal, or work a finding, risk, or assumption. Not for engineering change proposals, deviations, or waivers (ddna-change-control).

ddna-setup

Connect or reconnect DDNA in Claude, ChatGPT, or Codex by signing in to an existing DDNA account with OAuth. Use when DDNA is not connected or reports an authentication or permission failure.

ddna-standups

Read and answer DDNA daily stand-ups, and manage them for a workspace. Use when the user asks for their stand-up, wants to record today's answers, asks what the team reported, or (as a Workspace Manager or project lead) asks to set up or change a stand-up. Not for reading or changing the tasks themselves (ddna-tasks).

ddna-tasks

Read and manage DDNA project tasks, phases, review gates, roles, task plans, the Plan of Action and Milestones, and workspace organization tasks. Use when the user asks what they or their team must do next, or asks to create, assign, schedule, comment on, attach evidence to, or decide a task or gate. Not for adding people to a project or changing their access (ddna-project-admin), stand-up answers (ddna-standups), or engineering issues (ddna-engineering).