SPEC-005 claude/align-sidenav-styling-4MuxV
Preview & Sandbox Runes — Specification Specs
Draft 13
SPEC-007 claude/align-sidenav-styling-4MuxV
Local Runes — Declarative Rune Extension (v1) SPEC-010 claude/align-sidenav-styling-4MuxV
Theme Studio — AI-Powered Theme Generator 32/34 criteria
SPEC-021 main
Plan Runes Runes for spec-driven project management in AI-native development workflows. Package: @refrakt/plan.
0/5 criteria
SPEC-023 claude/align-sidenav-styling-4MuxV
Storytelling World Engine SPEC-029 claude/align-sidenav-styling-4MuxV
File-Derived Timestamps for Runes SPEC-031 claude/align-sidenav-styling-4MuxV
Vite Plugin — Framework-Agnostic Rune Integration 0/5 work items
SPEC-034 claude/align-sidenav-styling-4MuxV
Theme Structural Template Language (Design Exploration) SPEC-035 claude/align-sidenav-styling-4MuxV
Multi-Language Support SPEC-036 main
Claude Code Skills and Hooks for Plan Workflow Replace procedural CLAUDE.md instructions with Claude Code skills (custom slash commands) and hooks (automated enforcement) to make the plan workflow invocable, context-efficient, and enforceable.
SPEC-038 main
Git-Native Entity History Derive structured lifecycle timelines for plan entities from git history — attribute transitions, criteria progress, and resolution events — surfaced through the CLI and as a site rune.
SPEC-039 main
Plan Package Onboarding & Conventions Review Review and improve the @refrakt-md/plan package's conventions, folder structure, and onboarding experience. Three concerns drive this spec: the package is currently coupled to Claude Code as an AI tool, the folder naming convention uses singular nouns where plural would be more natural, and there is no path for users who already have planning documents to adopt the system.
SPEC-042 main
Plan Target for create-refrakt Add a planning-only scaffold option to create-refrakt so users who want to adopt refrakt primarily as a plan management tool have a one-command entry point, matching the experience for sites and themes.
1/1 work items
Review 4
SPEC-004 claude/align-sidenav-styling-4MuxV
Layout System — Specification SPEC-015 claude/align-sidenav-styling-4MuxV
Plan Site UX at Scale SPEC-028 claude/align-sidenav-styling-4MuxV
Rune Output Standards Accepted 20
SPEC-001 claude/align-sidenav-styling-4MuxV
Community Runes — Specification SPEC-002 claude/align-sidenav-styling-4MuxV
Cross-Page Pipeline — Specification SPEC-003 claude/align-sidenav-styling-4MuxV
Declarative Content Model — Specification SPEC-006 claude/align-sidenav-styling-4MuxV
Media Runes — Specification SPEC-011 claude/align-sidenav-styling-4MuxV
Rune: — High-Level Plan SPEC-012 claude/align-sidenav-styling-4MuxV
Rune Inspector — Transformation Pipeline Debugger for VS Code SPEC-013 claude/align-sidenav-styling-4MuxV
Multi-Framework Support: Layout Transform Architecture SPEC-014 claude/align-sidenav-styling-4MuxV
Plan Site via HTML Adapter SPEC-022 main
Plan CLI Plan management subcommands for the refrakt CLI. Package: @refrakt-md/plan.
0/4 criteria
SPEC-024 claude/align-sidenav-styling-4MuxV
Metadata System SPEC-025 claude/align-sidenav-styling-4MuxV
Universal Theming Dimensions SPEC-030 claude/align-sidenav-styling-4MuxV
Framework Adapter System SPEC-032 claude/align-sidenav-styling-4MuxV
Remove Legacy Model Class and Decorators SPEC-033 claude/align-sidenav-styling-4MuxV
Structure Slots and Declarative Flexibility SPEC-037 main
Plan Package Hardening Fix bugs, close validation gaps, implement knownSections for plan runes, and add missing CLI capabilities — all before building the Claude Code plugin layer (SPEC-036).
SPEC-040 main
Edge Runtime Compatibility for Plan Package Refactor @refrakt-md/plan so that its pure logic — parsing, diffing, filtering, relationship building, entity card construction — can be imported in edge runtimes (Cloudflare Workers, Deno Deploy, Vercel Edge Functions) without pulling in Node.js APIs (node:fs, node:child_process, node:path).
SPEC-041 main
Agent Rune Reference A CLI surface that lets a coding agent (Claude Code, Cursor, Copilot, etc.) discover the input syntax of any installed rune — tag name, attributes, content interpretation, and a minimal example — without invoking an LLM.
8/8 work items
Superseded 0
Deprecated 0