Skill: feature-workflow-artifacts (Cross-phase — Workflow + Artifacts)

You are enforcing the feature workflow and the documentation artifact standard used across all phases.

Purpose

• •Ensure every feature has a consistent, auditable paper trail.
• •Keep phases ordered and enforce “docs-only” phases.
• •Make it easy for any agent/human to resume work safely.

Inputs

• •A user requirement (or the most recent requirement text in chat)
• •Existing feature artifacts (if this is an iteration)

Outputs (required)

For each feature, the canonical directory is:

• •docs/features/<feature-slug>/

Canonical artifacts (required):

• •docs/features/<feature-slug>/00-requirement.md
• •docs/features/<feature-slug>/01-analysis.md
• •docs/features/<feature-slug>/02-design.md
• •docs/features/<feature-slug>/03-implementation-notes.md
• •docs/features/<feature-slug>/04-qa-report.md
• •docs/features/<feature-slug>/05-deployment-notes.md

Also update (required):

• •docs/features/FEATURE_INDEX.md (track status per feature)

Naming & structure conventions

Feature slug

• •Use kebab-case: my-feature-name
• •Slug should be stable over time (do not rename casually).
• •One feature = one slug directory.

Linking rule (traceability)

Each artifact should link to its neighbors using relative links, at minimum:

• •00-requirement.md links forward to placeholders for 01–05
• •01-analysis.md links back to 00 and forward to placeholders for 02–05
• •02-design.md links back to 01 and forward to placeholders for 03–05
• •03-implementation-notes.md links back to 02 and forward to placeholders for 04–05
• •04-qa-report.md links back to 03 and forward to placeholder for 05
• •05-deployment-notes.md links back to 04

Phase order (mandatory)

Every feature MUST progress in this order:

1. •Analyze
2. •Design
3. •Implementation
4. •Testing / QA
5. •Deployment

If a phase is not complete, do not proceed to the next phase.

Hard rules (workflow safety)

• •Analyze / Design / QA phases MUST NOT modify application code.
  • •Only feature artifacts and the feature index may be updated.
• •Implementation may modify application code, and MUST update 03-implementation-notes.md.
• •Deployment may modify documentation and minimal release configuration, and MUST write 05-deployment-notes.md.
• •If you detect requirement/design inconsistencies, missing requirements, or scope conflicts:
  • •record them in the current phase artifact
  • •stop and ask targeted questions

Phase completion criteria (minimum)

This skill defines the minimum “phase complete” bar. (Each phase skill may require additional sections/content.)

• •Analyze complete:
  • •01-analysis.md exists
  • •it includes assumptions, risks, inconsistencies, and labeled open questions (BLOCKING vs NON-BLOCKING)
• •Design complete:
  • •02-design.md exists
  • •it includes 3 options + decision + implementation plan + test plan
• •Implementation complete:
  • •code matches the chosen design plan
  • •03-implementation-notes.md exists and includes run/verify steps and migration status
• •Testing complete:
  • •04-qa-report.md exists
  • •it contains a clear verdict (Approved / Not Approved)
  • •no code changes were made during QA
• •Deployment complete:
  • •05-deployment-notes.md exists
  • •docs were updated as needed (user + technical)

Stop conditions (pipeline gates)

• •If Analyze has any BLOCKING questions: stop and do not design.
• •If Design has any BLOCKING questions: stop and do not implement.
• •If QA verdict is Not Approved: stop and do not deploy.

Relationship to phase skills

Use the phase skills for detailed requirements:

• •Phase 1: skills/feature-analyze/skill.md
• •Phase 2: skills/feature-design/skill.md
• •Phase 3: skills/feature-implement/skill.md
• •Phase 4: skills/feature-qa/skill.md
• •Phase 5: skills/feature-deploy/skill.md

This skill exists to centralize:

• •artifact names and locations
• •phase order and gates
• •traceability/linking expectations
• •minimum definition of phase complete