eng-feature-followup

To update engineering planning documents after a Jira change, provide the updated context to the pipeline. It orchestrates a sequenced revision across plans, designs, tests, tasks, and verifications while preserving unchanged sections.

Propagating Confluence changes across feature specs requires applying the updated context to the engineering pipeline. It revises all related planning artifacts, updates indexes, and generates a changelog to reflect the revision pass consistently.

You can preserve unchanged content when revising feature plans and tests. The pipeline applies updated context only to affected sections, ensuring existing unchanged documentation and verification artifacts remain intact during the update.

The feature plan update pipeline processes revisions by running five sequential stages. These stages systematically revise designs, tests, tasks, and verifications based on provided context, then automatically update indexes and changelogs.

The engineering update pipeline works with local spec documents. It accepts updated context from local files, Jira, or Confluence to coordinate revisions across all related planning artifacts and verification documents.

You need to run a full feature plan update pipeline when existing feature plans, designs, or tests require revision. It ensures that changes described by project management sources propagate consistently across all related engineering artifacts.