Zentao Project Story Management

Problem

In many Zentao workspaces, project stories are still entered manually while requirement docs live in Markdown. That creates a gap: a feature like F005 may exist in the doc but no one knows its Zentao ID, and updated descriptions may not reach the story record.

How It Works

The skill reads config.json for zentao_url, credentials, default_project, default_product, and requirements_doc. It obtains a token from /api.php/v1/tokens and reuses it as a zentaosid cookie or Token header.

• Create/edit: creation uses the built-in page endpoint because project-type story pools do not require a product field, while the REST create API does; editing first fetches the current story and submits only changed fields.
• Delete/query: uses REST endpoints DELETE /api.php/v1/stories/{storyID} and GET /api.php/v1/stories/{storyID}.
• Doc sync: headings are written as ### F001 - Feature name (#155). If #ID is present, the skill updates that story; if absent, it creates a story and writes the new ID back. Descriptions are converted to HTML with user story, prerequisites, feature points, optional field tables, and avoid English field names or UI styling.

Boundaries

It expects Python 3.7+ and requests. Create and edit requests require multipart/form-data with an empty files[] field. It manages story lifecycle and doc sync, not review, scheduling, or permission design; doc updates should be confirmed before syncing.