TFD-0009: Universal Request Folder Standard

TFD-0009: Universal Request Folder Standard

Status: Partially superseded by TFD-0026 (2026-05-28) — folder layout (request.md + input/process/output/) stands; folder name format {TYPE}-{DEPT}-{NNN}-{slug} is replaced by DAE-style {TYPE}-{NNNN}. See TFD-0026 for the new ID convention. Original status: Accepted Date: 2026-03-22 Decision makers: CEO (Oscar), CTO (Clara), Nomenclature Specialist (Nora)

Context

Factory workers each invented their own folder patterns for handling work requests. R&D used evaluations/{slug}/input/output/, frameworks used {framework}/input/, work orders used flat files with no consistent structure. There was no universal standard, making it hard to trace work, find requests, or understand what happened during execution.

Decision

Adopt a universal request folder standard that applies to all internal factory work and client production orders. Every request follows the same layout:

{TYPE}-{DEPT}-{NNN}-{slug}/
├── request.md          (or order.md for WO)
├── input/              (context from requestor)
├── process/            (thinking trail, drafts, decisions)
└── output/             (final deliverables)

Key Rules

  1. Two prefixes: REQ for internal factory requests, WO for client-facing work orders
  2. Department codes: CONS, CS, ENG, EXEC, ARCH, KM, METH, OPS, QA, PROD
  3. Format: {TYPE}-{DEPT}-{NNN}-{slug} — e.g., MET-0001-add-togaf-framework
  4. Location: Internal requests at departments/{dept}/requests/, work orders at production-lines/orders/, production internal at production-lines/requests/
  5. WO exclusivity: WO prefix is only used with PROD department code
  6. Metadata: YAML frontmatter in request.md/order.md with id, title, requestor, assignee, participants, status, created, completed, impacts

Versioning Rules

  • Requests are immutable once completed
  • To improve or revise an earlier output, create a new request referencing the original
  • The new output/ becomes the latest version; the original stays as history
  • No in-place mutation of completed requests

Tooling

Three skills support the standard:

  • /request-create — scaffolds a new request folder with correct naming, numbering, and template
  • /request-status — regenerates company/requests-registry.md from all frontmatter
  • /request-close — marks a request as completed or cancelled

Registry

Auto-generated index at company/requests-registry.md provides factory-wide visibility. Future Jira sync point.

Rationale

  • Traceability: Every piece of work has a folder with input, process trace, and output
  • Discoverability: Department managers can browse requests/ to see all work in their area
  • Versioning: Immutable requests create a natural audit trail
  • Consistency: Same pattern whether you're evaluating a tool, building a framework, or producing a digital talent
  • Future-ready: Registry structure supports Jira sync when needed

Migration

  • 4 R&D evaluations migrated to RD-0001 through RD-0004
  • 2 work orders migrated to WO-0001 and WO-0002
  • Nora's naming standards updated (replaced "Evaluation Request Naming" with "Request/Order Naming")
  • /rd-evaluate skill updated to use new paths

Future Follow-ups

  • TFD-0008 notification integration: request creation/completion should trigger notifications per the process interrelation standard
  • Jira sync via the registry
  • Update all role.md files to reference requests/ as a standard department directory
  • Controlled vocabulary for impacts fields (process, capability) as patterns emerge

References

  • Full spec: docs/superpowers/specs/2026-03-22-request-folder-standard-design.md
  • Implementation plan: docs/superpowers/plans/2026-03-22-request-folder-standard.md
  • Naming standards: departments/methodology/nomenclature-specialist-nora/standards/naming-conventions.md