[clubanderson]

Adds spektacular voice --from <plaud|wisprflow|file|stdin> [--latest|--title X|--path P] [--publish --repo owner/repo]: fetches one voice note (Plaud via its free MCP server over stdio, Wispr Flow local history, a transcript file, or text on stdin), drafts it onto the spec scaffold, and either starts the seeded spec interview or, with --publish, writes the spec final and files it through publish as an RFC + one child issue per requirement, printing the URLs.
Also serves a non-interactive agent in a hive pod seeded from a transcript on stdin/file (no Plaud MCP in the agent); the spek-new skill now says how to finish from pasted transcript text without asking.
Tests: fake MCP over pipes (no sleeps), fake GitHub for the publish chain, template wording pins. README: "Voice → spec → hive" quickstart.
Closes #122.

[clubanderson]

/approve
/lgtm

[kubestellar-prow]

@clubanderson: you cannot LGTM your own PR.

Details

In response to this:

/approve
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[clubanderson]

/approve
/lgtm

[kubestellar-prow]

@clubanderson: you cannot LGTM your own PR.

Details

In response to this:

/approve
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: clubanderson
Once this PR has been reviewed and has the lgtm label, please assign nicholasjackson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hivecommons-hive]

Please narrow this to #122’s stated scope before landing; there is also a filesystem write defect.

• Medium — validate names before staging (cmd/voice.go:125–127). The non-publish path joins the raw --name into the material directory and calls writeVoiceMaterial before runSpecNew validates it. For example, --name ../../../victim resolves the staging directory to <project>/victim; writeVoiceMaterial (cmd/voice.go:279) overwrites existing note.md, transcript.md, and draft.md there. Only afterward does identifier.NormalizePart reject the separators. Validate the name before any staging write and keep the destination inside the staging directory.
• Medium — the CLI/MCP implementation contradicts the linked issue (cmd/voice.go:26, internal/voice/plaud.go:14). Per #122, this is explicitly a wording-only change, with no CLI MCP client because fetching belongs to the driving agent. This adds that client plus a publish path and vendor integrations. The template edits address the requested workflow; the additional implementation should be removed from this PR or separately scoped.

@nicholasjackson, please review the trust implications if the CLI addition is retained: its default executes npx -y @plaud-ai/mcp@latest (internal/voice/plaud.go:14), and the child inherits the full environment (internal/voice/mcp.go:233), including any available publisher credentials.

Reviewed the changed code, identifier validation, spec-start callers, publisher, tests, PR body and #122 (no comments). Existing build-and-test checks passed. Local test execution was blocked by the reviewer wrapper; registry lookup also failed on an unavailable sibling checkout.

— hive: agent=reviewer backend=codex model=gpt-6.1-sol codex=0.167.0

[clubanderson]

Closing in favour of #124, which carves out just the part #122 asked for: the wording-only change to the spek-new skill and the seeded interview step (the first commit of this PR, unchanged).

Not carried over, and why:

• The in-binary Plaud MCP client and Wispr Flow reader: ✨ spec: start a spec from a voice recording (Plaud / any recorder MCP) #122 and the epics-and-seeded-specs design keep fetching on the agent side. The client also ran npx -y @plaud-ai/mcp@latest (unpinned) with the full environment inherited by the child.
• --name was joined into the staging directory and written before it was validated (cmd/voice.go), so --name ../../../x could overwrite files outside it. That code goes away with the command.
• The --publish chain (transcript to RFC + child issues) is the only new capability here. If Hive's Inbox needs a one-step path, it should come back as its own narrowly scoped PR using the existing publish command.

Direction going forward: anything in Hive should be usable as input to Spek, by reference (provenance URIs) rather than one vendor integration per source.