skills.rest
zerobias-org
zerobias-orgOFFICIAL
Explore all skills by this author →
WebsiteGitHub

name-phase-outputs

Enforce standard phase output file naming and path conventions across module lifecycles.

6|Updated Feb 20, 2025
Search Tags:#workflow#documentation#audit#traceability#naming-conventions#phase-outputs
One-click install
npx skills add https://github.com/zerobias-org/module --skill name-phase-outputs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: name-phase-outputs
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/name-phase-outputs
Command: npx skills add https://github.com/zerobias-org/module --skill name-phase-outputs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill standardizes how phase output artifacts are named and organized, ensuring consistent, traceable memory of each module's lifecycle.

Core Features & Use Cases

  • Enforces the standard path format for phase outputs: .claude/.localmemory/create-{module-identifier}/phase-01-discovery.json, phase-02-scaffolding.json, and so on
  • Provides phase-by-phase naming conventions from phase 01 through 09, plus sub-step outputs, to support reproducible automation
  • Defines governance for the entire lifecycle to aid auditing and cross-team collaboration

Quick Start

Apply the standard naming convention to your module's phase outputs and store them under the advised path.

Frequently Asked Questions about name-phase-outputs

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

FAQPage Schema
How do I enforce consistent naming conventions for phase output files?▼

To enforce consistent phase output naming, apply standard path and file formats like .claude/.localmemory/create-{module-identifier}/phase-01-discovery.json across your module lifecycle for traceability.

What is the standard path format for saving module lifecycle artifacts?▼

The standard path format for module lifecycle artifacts is .claude/.localmemory/create-{module-identifier}/, storing files like phase-01-discovery.json and phase-02-scaffolding.json for each phase.

How do I document phase outputs for cross-team workflow auditing?▼

Document phase outputs for auditing by enforcing per-phase naming conventions from phase 01 through 09, plus sub-step outputs, under a standard local memory path to ensure reproducible traceability.

When do I need standardized phase output traceability for my workflow?▼

You need standardized phase output traceability when managing module lifecycles from discovery through final validation, requiring reproducible automation and cross-team collaboration governance.

Can I customize the file naming format for sub-step phase outputs?▼

The standard enforces specific file naming formats for phase outputs and sub-step outputs to maintain strict traceability, meaning customizing the naming format is not recommended as it breaks lifecycle governance.

Related Skills

Explore More Software Engineering Skills→
matdev83matdev83

golang-project-layout

Guide Go project structuring with directory layout and module naming conventions.

Community
Intermediate
catlog22catlog22
511

maestro-milestone-complete

Archive completed milestones and update project state in repository workflows.

Community
Advanced
HuuBarHuuBar

template-skill

Creates a standardized Skill scaffold with SKILL.md frontmatter file and discovery metadata.

Community
Basic
ajianazajianaz
4

docs-generator

Generate AGENTS.md and agent.d documentation for AI coding agents.

Community
Basic