PHI LOOP

Automate the 9-phase spec-first development workflow for t27 ternary AI silicon projects.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/gHashTag/t27 --skill phi-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PHI LOOP
Source: https://github.com/gHashTag/t27/tree/main/.claude/skills/phi-loop
Command: npx skills add https://github.com/gHashTag/t27 --skill phi-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent, untraceable development practices for t27 ternary AI silicon projects by enforcing a standardized, law-compliant workflow from initial issue to merged, verified code.

Core Features & Use Cases

  • 9-Phase End-to-End Workflow: Guides teams through every step from issue tracking and .t27 spec writing to test-driven development, RTL generation, conformance verification, and merge to main.
  • Invariant Law Enforcement: Automatically enforces all 7 t27 invariant laws including commit traceability to issue tickets, prohibition of manual edits to generated files, and mandatory test coverage in specifications.
  • Integrated CLI Support: Works with the tri command-line tool to advance phases, check status, and reset rings without manual workflow tracking.
  • Use Case: A developer working on a new GF16 numeric format extension can use this Skill to automatically track their progress through each workflow phase, run conformance tests, and seal generated artifacts without manual status tracking.

Quick Start

Use the phi-loop skill to execute the complete 9-phase spec-first development workflow for your active t27 project ring.

Frequently Asked Questions about PHI LOOP

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

FAQPage Schema
What is a spec-first development workflow for ternary AI silicon?

A spec-first development workflow for ternary AI silicon standardizes the end-to-end process from issue tracking and .t27 spec writing to test-driven development, RTL generation, and conformance verification before merging to main.

How do I automate conformance testing and RTL generation for t27 projects?

Automate conformance testing and RTL generation for t27 projects by executing a 9-phase workflow that advances through specification, test-driven development, code generation, and verification using the tri command-line tool.

How do I enforce invariant compliance and commit traceability in spec-first development?

Enforce invariant compliance and commit traceability in spec-first development by applying automated checks that require issue ticket references in commits, prohibit manual edits to generated files, and mandate test coverage in specifications.

Does the tri CLI tool support automated phase tracking for t27 ternary silicon projects?

Yes, the tri CLI tool supports automated phase tracking for t27 ternary silicon projects by allowing developers to advance phases, check status, and reset rings without manual workflow tracking.

What are the limitations of manually editing generated files in a t27 spec-first workflow?

Manually editing generated files in a t27 spec-first workflow violates invariant laws, breaks automated traceability from issue tracking to merge, and prevents proper conformance verification of the generated RTL artifacts.

When do I need a full 9-phase workflow for t27 ternary silicon development?

You need a full 9-phase workflow for t27 ternary silicon development whenever a task requires complete traceability from issue tracking through specification, test-driven development, code generation, verification, and merge to main.