fc-change-log

Updated Apr 14, 2026

Search Tags:#version control #change management #impact assessment #Atlassian #Functional Document

Ready to run

npx skills add https://github.com/wam-leadclic/functional-consultant-assistant-skills --skill fc-change-log

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fc-change-log
Source: https://github.com/wam-leadclic/functional-consultant-assistant-skills/tree/main/skills/fc-change-log
Command: npx skills add https://github.com/wam-leadclic/functional-consultant-assistant-skills --skill fc-change-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires confluence, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all changes to the Functional Document after client sign-off are properly registered, tracked, and documented, maintaining the integrity of the contract and downstream artifacts.

Core Features & Use Cases

Change Registration: Record changes to the Functional Document with detailed descriptions and impact assessments.
Impact Assessment: Evaluate the impact of changes on UAT test cases, training materials, and FDRs.
Version Control: Generate new document versions and maintain a history of changes.
Use Case: When a Scope Change Request is approved, use this Skill to document the change, assess its impact, and update the Functional Document accordingly.

Quick Start

Use the fc-change-log skill to register a change to the Functional Document after client sign-off.

Frequently Asked Questions about fc-change-log

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

FAQPage Schema

How do I manage changes to a Functional Document after client sign-off in Salesforce?▼

To manage changes to a Functional Document after client sign-off, you need an approved Scope Change Request. This ensures changes are registered, tracked, and documented while maintaining contract integrity and downstream artifacts.

What is the process for impact assessment when updating a signed-off Functional Document?▼

Impact assessment for a Functional Document involves evaluating how changes affect UAT test cases, training materials, and FDRs. This ensures all downstream artifacts remain aligned with the updated requirements.

Does this change management workflow require Atlassian Confluence integration?▼

Yes, this change management workflow requires Atlassian integration for Confluence document management. It uses Confluence to generate new document versions and maintain a comprehensive history of changes.

How do I register a Scope Change Request against an existing Functional Document?▼

To register a Scope Change Request against a Functional Document, ensure the request is approved first. Then, document the change description, perform an impact assessment, and update the document version.

Can I track version control history for Functional Documents in Confluence?▼

Yes, you can track version control history for Functional Documents in Confluence. The workflow generates new document versions and maintains a detailed history of registered changes and their impacts.

What happens if I update a Functional Document without an approved Scope Change Request?▼

Updating a Functional Document without an approved Scope Change Request breaks traceability and contract integrity. The workflow requires both a signed-off document and an approved request to proceed.