prompt-session-intake

Captures durable project intent from bound direct prompts into canonical workflow objectives.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill prompt-session-intake-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-session-intake
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/prompt-session-intake
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill prompt-session-intake-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Direct user prompts in an agent session often contain durable project decisions, constraints, and acceptance criteria that get lost between turns. This Skill provides a non-blocking capture sidecar that records only durable project intent from direct prompts bound to a Task Implementer or Agentic SDLC workflow, without ever blocking the user's request or starting a workflow. ## Core Features & Use Cases - Non-blocking capture: The UserPromptSubmit hook always passes the direct prompt through; it stages only metadata (identity, digest, workflow, token, timing) and never persists the submitted prompt body. - Disposition classification: The current agent records exactly one disposition per turn: merge (durable intent), noop (control/status/conversation turns), or sensitive (discards all capture authority). - Exactly-once canonical merge: Accepted project-intent projections are merged into the canonical workflow prompt via compare-and-set with operation-and-projection markers, so retries and byte-identical duplicates never append twice. - Use Case: After running $task-implementer workspace init, a user says "Require exactly three bounded retries for the API client." The skill stages the event, classifies it as a constraint merge, projects the durable intent, and merges it into the canonical objective exactly once while the agent answers normally. ## Quick Start Invoke an exact $task-implementer workspace init or run command to bind your session, then continue prompting normally and the capture sidecar will handle durable intent automatically.

Frequently Asked Questions about prompt-session-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture project intent from direct prompts in a Codex session?

Bind the session first with an exact $task-implementer workspace init, $task-implementer run, $sdlc-start workspace init, or $sdlc-start run command. Later direct turns in that session become capture-eligible, and the hook stages metadata while the agent records merge, noop, or sensitive.

What prompt content gets merged into the canonical workflow objective?

Only durable project intent merges: objectives, scope, behavior, API/CLI/configuration contracts, architecture decisions, constraints, acceptance outcomes, facts, examples, corrections, and operational requirements. Workflow control, shell actions, status requests, and conversation are recorded as no-ops.

Does prompt capture block or delay the agent's response?

No. Every UserPromptSubmit result is non-blocking and the direct prompt always reaches the current agent. Capture failures, secrets, or invalid state skip capture with bounded evidence and never stop the turn or request a Stop continuation.

What happens when a prompt contains secrets or sensitive content?

Recognized secrets are skipped before any event or projection is written, and mixed secret-bearing prompts are never partially captured. If sensitive content is found after staging, the sensitive disposition atomically discards the digest, operation ID, token, and projection authority.

Can I trigger prompt-session-intake manually as a standalone command?

No. It is an internal coordinator-only skill with no public binding, accept, consume, replay, or recovery command. It activates only when its hook supplies an exact current-turn event path and acceptance token for a bound session.

How are duplicate or retried prompt merges handled?

Each merge carries one operation-and-projection marker; an exact operation retry returns the already-applied result, and a byte-identical projection under another operation is a terminal duplicate no-op. Concurrent same-base merges keep one winner and one drift result without auto-rebase.