nw-finalize

Finalize completed features by creating evolution documents, migrating artifacts, and cleaning workspaces.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-finalize-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-finalize
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-finalize
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-finalize-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives finalized features by creating an evolution document, migrating artifacts to permanent locations, and cleaning the temporary workspace after validation.

Core Features & Use Cases

  • Create and store a post-mortem evolution document for completed features.
  • Migrate lasting artifacts to permanent directories (architecture docs, ADRs, scenarios, etc.).
  • Clean up temporary workspaces while preserving essential artifacts and leaving a clear audit trail.

Quick Start

Run the NW-FINALIZE workflow for a feature by supplying the agent and feature-id.

Frequently Asked Questions about nw-finalize

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

FAQPage Schema
How do I automate feature finalization and workspace cleanup after validation?

Feature finalization is automated by creating an evolution document, migrating lasting artifacts to permanent directories, and cleaning the temporary workspace after validation passes.

What is the best way to preserve architecture docs and ADRs when cleaning up a temporary workspace?

Workspace cleanup preserves artifacts by migrating lasting architecture docs, ADRs, and scenarios to permanent directories before removing temporary files, leaving a clear audit trail.

How does artifact migration work for completed feature delivery?

Artifact migration moves validated feature artifacts from temporary directories to permanent locations, ensuring essential governance documentation is preserved while workspace hygiene is maintained.

Do I need an evolution document to satisfy governance requirements for feature gating?

Yes, an evolution document is required to satisfy governance requirements for gating, documentation, and artifact migration during the feature finalization process.

Can I finalize a feature without losing essential artifacts in the temporary workspace?

Finalizing a feature preserves essential artifacts by executing a four-phase process that covers evolution, migration, cleanup, and verification, ensuring no critical files are lost.

What are the limitations of workspace cleanup for feature delivery workflows?

Workspace cleanup is limited to feature delivery workflows within nWave where artifacts must be explicitly preserved and validation has already been completed prior to finalization.