agentic-sales-spec

To convert an agentic-sales roadmap phase into specification documents, the Skill selects the next unchecked phase and generates requirements, plan, and validation docs aligned to the project constitution. It runs a mandatory 3-axis interview before outputting text files.

Generating architecture contracts for audio pipeline and UI routing changes requires converting requirements into precise specification documents. The Skill writes contract-accurate requirements, plan, and validation docs without implementing feature code.

The 3-axis AskUserQuestion interview works by asking structured questions about scope, decisions, and context before writing specification files. This mandatory interviewing step resolves ambiguity up front to ensure contract-accurate documentation.

No, you cannot use this to write feature code for Rust and TTS pipeline changes. The Skill outputs documentation only, generating specification files for requirements, plan, and validation, and stops for human review after creating the three files.

You need to provide an agentic-sales roadmap phase or a pasted requirement to generate validation gates and architecture specs. The Skill selects the next unchecked phase from the roadmap to produce a dedicated spec directory for the documentation.

Development drifts during outline and JSON propagation tasks due to a lack of precise, contract-aligned specification documents. Translating roadmap phases into dedicated spec directories for requirements, plan, and validation prevents drift by enabling safe implementation.