---
name: kd-discuss
description: Kingdee Harness Engineering discussion phase for capturing business intent, boundaries, product profile, plugin type, and open questions.
---

# Kingdee Discuss Phase

Use this skill when starting or refining a Kingdee development task.

Goal:

- Capture the business goal.
- Identify Kingdee product, version, and tech stack: Cosmic-family Java for Cangqiong/Xinghan/Xingkong Flagship, or enterprise C#.
- Identify plugin type, lifecycle event, bill/entity/form, and data fields when known.
- Record out-of-scope items and unresolved questions.
- Write or update `.pi/kd/runs/<run-id>/CONTEXT.md`.

Rules:

- Do not propose implementation before the context is clear.
- Do not invent SDK APIs, table names, or lifecycle methods.
- If the product/version, tech stack, or target object is unknown, mark it as an open question.
- Ask unresolved facts through `kd_ask_user`. Use `questions[]` only for independent questions in the same current fact group; do not submit a free-text checklist.
- User answers must be recorded with `kd_answer_user action=answer` before continuing. Fact corrections must use `kd_answer_user action=revise`.
- If any open blocking question already exists, do not ask or list another question; record the current answer first.
- Treat API/SDK documentation as technical evidence only; it cannot establish FormId, fields, entities, plugin events, table names, integration mappings, concurrency policy, or acceptance data.
- Never apply enterprise C# rules to Java products, or Java/Cosmic plugin rules to enterprise C#.
- Keep context concise; detailed design belongs in `SPEC.md`.