TAPD Requirement Sync

Usage Scenarios

• Users need to sync, update, push changes, or resubmit requirements
• The Markdown file already contains

  tapd_id

• The goal is to keep TAPD and local Markdown in sync

Execution Steps

1. Read the Markdown file.
2. Verify that

   tapd_id

   exists in the frontmatter.
3. Execute:

tapd story update <markdown-file>

1. Verification:
   • The update is executed successfully

   • updated_at

     is written back to the local file

Notes

• If the original

  tapd_id

  does not exist in TAPD, the CLI will automatically recreate the requirement
• Local images and Mermaid diagrams are processed during synchronization