eng-feature-followup

Coordinate engineering planning updates across plans, designs, tests, tasks, and verifications.

1|Updated Jun 7, 2024

Search Tags:#planning #changelog #documentation #verification #engineering #update

Ready to run

npx skills add https://github.com/jsco2t/dotfiles --skill eng-feature-followup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eng-feature-followup
Source: https://github.com/jsco2t/dotfiles/tree/main/.claude/skills/eng-feature-followup
Command: npx skills add https://github.com/jsco2t/dotfiles --skill eng-feature-followup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates updates through the full engineering planning pipeline to revise an existing feature's documentation and verification artifacts, ensuring changes propagate consistently.

Core Features & Use Cases

Orchestrates a sequenced update run across plans, designs, tests, tasks, and verifications for an existing feature.
Preserves unchanged sections while applying updated context from Jira/Confluence/file sources.
Generates an updated changelog and index entries to reflect the revision pass.

Quick Start

Provide the updated context to begin the update pipeline, and the system will run the five update stages in the exact order.

Frequently Asked Questions about eng-feature-followup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update engineering planning documents when a feature changes in Jira?▼

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.

What is the best way to propagate Confluence changes across existing feature specs?▼

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.

Can I preserve unchanged content when revising feature plans and tests?▼

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.

How does the feature plan update pipeline process revisions step by step?▼

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.

Does the engineering update pipeline work with local spec documents?▼

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.

When do I need to run a full feature plan update pipeline?▼

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.