qiqi-project

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

企企服务业ERP项目领域

QIQI Service Industry ERP Project Domain

本技能定义项目领域专用命令入口、分析口径和结果判断。当前参数以 qiqi 目标叶子命令

--help

为准。

This skill defines the dedicated command entry, analysis criteria and result judgment for the project domain. Current parameters are subject to the qiqi target leaf command

--help

领域事实边界

Domain Fact Boundaries

项目是任务、工时和业财事实的归集范围；名称只产生候选，稳定
```
Project:<id>
```
或唯一编码才确认项目。
任务可能同时承担项目计划/WBS与日常执行两类用途。本技能的专用写入路径只处理当前运行时公开的任务命令；计划层级、汇总规则和依赖关系必须由当前对象元数据确认。
工时是人员在业务自然日向项目或任务归集的投入事实；其单据阶段、成本归集和预算控制规则以当前企业配置为准，不从一次登记直接推断。
经营分析沿预算、收入、成本和现金四类事实展开：合同、收入确认与开票不等于收款；成本发生不等于付款；预算不等于执行。

Project is the collection scope for tasks, working hours and business-finance facts; the name only generates candidates, and a stable
```
Project:<id>
```
or unique code is required to confirm the project.
Task may serve both project planning/WBS and daily execution purposes. The dedicated write path of this skill only processes task commands publicly available in the current runtime; planning levels, summary rules and dependency relationships must be confirmed by the current object metadata.
Working Hours are the input facts that personnel allocate to projects or tasks on business natural days; the document stage, cost allocation and budget control rules are subject to the current enterprise configuration and cannot be directly inferred from a single registration.
Business Analysis is carried out along four types of facts: budget, revenue, cost and cash; contracts, revenue recognition and invoicing do not equal collection; cost occurrence does not equal payment; budget does not equal execution.

当前 profile 公开 project 域时的操作入口

Operation Entries When Current Profile Exposes the Project Domain

只有当前 profile 的

qiqi --help

出现

project

域时，才读取并使用对应叶子命令；未公开时报告能力缺口，不把以下入口当作固定能力。

业务意图	使用的命令
创建项目任务、日常任务或子任务	`project task create`
修改任务业务属性	`project task update`
开始任务	`project task start`
完成任务	`project task finish`
登记项目或任务工时	`project work-hours log`

任务开始和完成不使用

do-action

。不得因为通用动作名称相近而建立第二条执行路径。

Only when

project

domain appears in

qiqi --help

of the current profile, the corresponding leaf commands are read and used; if not exposed, report the capability gap and do not treat the following entries as fixed capabilities.

Business Intent	Command Used
Create project tasks, daily tasks or subtasks	`project task create`
Modify task business attributes	`project task update`
Start a task	`project task start`
Complete a task	`project task finish`
Log project or task working hours	`project work-hours log`

Do not use

do-action

for starting and completing tasks. Do not establish a second execution path due to similar general action names.

工作原则

Work Principles

使用目标 profile 的
```
auth status
```
核对当前企业和用户；profile 已明确且刚验证过时不重复执行。
用
```
objects
```
、
```
seek
```
、
```
find list
```
和
```
records get
```
按需取得唯一项目、任务和人员引用；已有稳定引用时直接核对必要记录。
查询前明确项目范围、业务期间、事实阶段和完整性要求；处理完整分页和大输出后再形成统计结论。
写入前读取目标叶子命令
```
--help
```
，只发送用户意图需要的最小参数；未展开的可写字段按「写入保护」处理。
根据返回的稳定引用、记录阶段和关键字段验证结果。超时或结果不明确时先查询，不直接重试。

Use
```
auth status
```
of the target profile to verify the current enterprise and user; do not repeat execution if the profile is clear and just verified.
Use
```
objects
```
,
```
seek
```
,
```
find list
```
and
```
records get
```
to obtain unique references to projects, tasks and personnel as needed; directly check necessary records when stable references already exist.
Clarify the project scope, business period, fact stage and integrity requirements before querying; process complete pagination and large outputs before forming statistical conclusions.
Read the target leaf command
```
--help
```
before writing, and only send the minimum parameters required by the user's intent; unexpanded writable fields are handled according to "Write Protection".
Verify results based on returned stable references, record stages and key fields. Query first instead of directly retrying when timeout or results are unclear.

写入保护

Write Protection

项目任务、日常任务和子任务是不同意图；没有项目时不把项目工作降级为日常任务。
不创建占位项目、占位人员或占位任务来满足工时登记。
项目和父任务是结构上下文，不作为普通字段重复写入；状态、来源、审计和计算字段由业务规则维护。
创建任务返回草稿或其它阶段时按返回事实报告，不把创建成功表述为已提交、已开始或已完成。
每次执行都是一次独立的业务意图，CLI 不在多次调用之间去重。重跑任务创建或工时登记会再写入一条，结果不明确时先核查业务事实再决定。
明确批量处理同一父任务下的子任务时，开始、完成等写操作默认串行；前一项结果明确后再处理下一项，避免并发写入冲突。
计划开始、计划完成、实际开始、实际完成和工时日期都是业务自然日，具体格式以当前字段和命令描述为准。

Project tasks, daily tasks and subtasks have different intents; do not downgrade project work to daily tasks when there is no project.
Do not create placeholder projects, placeholder personnel or placeholder tasks to meet working hour registration requirements.
Projects and parent tasks are structural contexts and are not repeatedly written as ordinary fields; status, source, audit and calculation fields are maintained by business rules.
Report according to the returned facts when creating a task returns a draft or other stages, and do not describe creation success as submitted, started or completed.
Each execution is an independent business intent; the CLI does not deduplicate between multiple calls. Re-running task creation or working hour registration will write another record; check business facts first before deciding when results are unclear.
When explicitly processing multiple subtasks under the same parent task in batches, write operations such as starting and completing are serial by default; process the next item only after the previous result is clear to avoid concurrent write conflicts.
Planned start, planned finish, actual start, actual finish and working hour dates are all business natural days; the specific format is subject to the current field and command description.

未展开的可写模型字段

Unexpanded Writable Model Fields

任务创建、任务修改和工时登记共用本规则。

模型元数据决定字段是否存在、技术名、数据类型和可写性；命令输入定义只决定哪些字段被展开为一级选项。用户需要录入的字段已在当前模型元数据中定义且可写、但未在目标命令中展开时，才属于本节处理范围。

先确认字段技术名、数据类型以及引用、枚举或布尔字段的候选值。模型元数据未定义，或属于状态、来源、审计、计算字段时，不构造或写入。

确认后，使用目标命令的

--data

传递完整业务参数对象；

--data

与逐字段选项互斥。已展开的标准字段与未展开的可写字段同时需要写入时，也统一放入同一个 JSON 对象，不拆成未经确认的命令选项。

This rule applies to task creation, task modification and working hour registration.

Model metadata determines whether a field exists, its technical name, data type and writability; command input definitions only determine which fields are expanded as first-level options. This section applies only when the field that the user needs to enter is defined and writable in the current model metadata but not expanded in the target command.

First confirm the field's technical name, data type and candidate values for reference, enumeration or boolean fields. Do not construct or write if the model metadata does not define it, or if it belongs to status, source, audit or calculation fields.

After confirmation, use

--data

of the target command to pass the complete business parameter object;

--data

is mutually exclusive with field-by-field options. When both expanded standard fields and unexpanded writable fields need to be written, put them into the same JSON object uniformly instead of splitting into unconfirmed command options.

按需读取

On-Demand Reading

需要理解任务意图、结构、计划与执行工作流时，读取 task-workflows.md。
需要登记或解释项目投入、工时成本与计费依据时，读取 work-hours.md。
用户询问项目利润、花费方向、回款或现金情况时，读取 project-profit-analysis.md。
用户询问预算金额、执行金额、差异或超预算时，读取 project-budget-execution.md。

只读取当前任务需要的引用文件。

Read task-workflows.md when you need to understand task intent, structure, planning and execution workflows.
Read work-hours.md when you need to register or explain project input, working hour costs and billing basis.
Read project-profit-analysis.md when users ask about project profits, spending directions, payment collection or cash status.
Read project-budget-execution.md when users ask about budget amount, execution amount, variance or over-budget status.

Only read reference files required for the current task.