Skip to content

Add change proposal for interactive proposal QA command - #97

Closed
TabishB wants to merge 1 commit into
mainfrom
codex/design-interactive-proposal-qa-process
Closed

Add change proposal for interactive proposal QA command#97
TabishB wants to merge 1 commit into
mainfrom
codex/design-interactive-proposal-qa-process

Conversation

@TabishB

@TabishB TabishB commented Sep 30, 2025

Copy link
Copy Markdown
Contributor

Summary

  • plan a /openspec/proposal-qa discovery interview that analyses requests, asks option-backed clarifying questions, and produces a reusable summary
  • extend init/update expectations so all assistants ship a matching proposal-qa slash command alongside existing proposal/apply/archive helpers
  • outline implementation tasks covering template updates, onboarding writers, conversational heuristics, and validation steps

Testing

  • node bin/openspec.js validate add-interactive-proposal-qa --strict

https://chatgpt.com/codex/tasks/task_e_68db3388e21483228737449d47f63d4d

@KeentGG

KeentGG commented Oct 1, 2025

Copy link
Copy Markdown

that spec sounds good for me, the original requirements builder formulated questions to be answerable by yes/no i think to lessen cognitive load for the user. However let's see how it would go with 2-4 answer options, maybe it'll lead to more precised context gathering or worst case just adds cognitive with minimal benefit.

The codex link you posted i think wasn't public, can't access it.

@Jacubeit

Copy link
Copy Markdown

played around with this approach after having sonnet4.5 implement this spec.
Works well, was nice experience. we had 6 QA, then discovered we need more and did an extra round.
Like the usual sonnet4.5 way it derailed at the end and started implementing instead of writing the specs.
great work btw.

@TabishB TabishB closed this Jan 30, 2026
timothybrush pushed a commit to timothybrush/OpenSpec that referenced this pull request Aug 12, 2026
…ssion-AI#1635)

Resolve all three open Dependabot alerts (all high severity):

- GHSA-5p4m-2wfm-xmqj — js-yaml quadratic-CPU !!omap DoS (Fission-AI#96, Fission-AI#97).
  Root tree carried js-yaml 3.15.0 (via read-yaml-file) and 4.3.0 (via
  @changesets/parse). Dev-only; never in the published CLI, which uses
  `yaml`, not `js-yaml`. Pinned to >=3.15.1 / >=4.3.1.
- GHSA-2v37-7h3g-55p8 / CVE-2026-67213 — nanoid size=0 infinite loop (Fission-AI#99).
  Present in both root (dev, via postcss<-vitest) and website (build-time,
  via postcss<-next) trees. Pinned to >=3.3.17 (resolves to 3.3.18).

Overrides added to all four override surfaces (pnpm-workspace.yaml +
package.json, root and website) to keep them in sync, each YAML entry
annotated with its advisory id and removal condition.

flake.nix pnpmDeps FOD hash regenerated for the root lockfile change
(verified via nix build; hash-mismatch-count 0). dependabot.yml gains a
note documenting the two surfaces Dependabot cannot manage (pnpm
overrides + the Nix flake).

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants