Intent
Shipyard's internal requirements intake for non-engineer contributors (support/ops), ...
Install
npx skills add Yeachan-Heo/oh-my-claudecode --skill intent -g -a claude-code -y- Repository
- Yeachan-Heo/oh-my-claudecode40.5k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,405 tokens
- Runs scripts
- No, instructions only
What it does
Shipyard's internal requirements intake for non-engineer contributors (support/ops), turn a pasted chat log or verbal problem report into a five-section intent.md through numbered batch questioning with a completion gate, walk it through tracker review with harbor's four records, and hand the accepted intent to /launch as its mission brief. Produces decisions, not code.
Intent
Intent is the shipyard's internal intake: support/ops staff see product problems first but cannot write engineering specs. The intent skill converts their conversation into a goal-level YAML+markdown artifact that an owner reviews and signs, so engineering receives a fog-free mission. It stands on the verifiability boundary, the agent asks, records, and drafts; humans submit, verify, and sign.
Design provenance: every decision here was pinned by a wayfinder map (7 tickets) and walked end-to-end in a demo repository before implementation.
Role contract
- The contributor (e.g. support staff) pastes raw feedback or a chat log. The agent never invents facts; unknowns become explicit
待确认items. - Decisions are the humans': the contributor confirms wording, the supervisor submits, the product owner verifies facts and signs accept/reject. The agent never signs, never rejects on anyone's behalf, and never stands in for a reviewer.
- The stop gate is a completion gate, not an ambiguity score, no math is borrowed from deep-interview; only its Goal and Constraint clarity judgments are reused as quality bars.
