Skill Claude CodeCodex
Phase 1 of the SDD workflow: capture and validate requirements in one pass. Owns the full Define methodology — classify the input (BRAINSTORM document, meeting notes, email thread, conversation, or direct request), extract entities (problem, users, MoSCoW goals, success criteria, acceptance tests, constraints, out of…
Skill Claude CodeCodex
Create the architecture and technical specification for a defined feature — Phase 2 of the SDD workflow. Transforms a validated DEFINE document into a DESIGN document: architecture diagram, components, inline architecture decision records, an agent-matched file manifest, KB-grounded code patterns, and a testing…
Skill Claude CodeCodex
Update an existing SDD phase document (BRAINSTORM/DEFINE/DESIGN) mid-stream with full cascade awareness: classify the change (additive, modifying, removing, architectural), apply it with a version bump and change note, walk the cascade rules for downstream impact, and confirm with the user before applying any…
Skill Claude CodeCodex
Archive a completed feature and close the SDD cycle (Phase 4): verify the build is truly complete, archive every phase artifact, capture lessons learned, update all phase documents to Shipped, and clean the working folders. Carries the full ship methodology — verification order, ship readiness matrix, the concrete…
Skill Claude CodeCodex
Spec-Driven Development workflow guidance for structured feature development. Use PROACTIVELY when the user discusses building features, planning implementations, capturing requirements, designing architectures, or shipping completed work. Guides through the 5-phase SDD workflow: Brainstorm → Define → Design → Build →…
Skill Claude CodeCodex
Generates the user's daily standup message in the Done / Will do / Blockers format from git history, PRs/issues, and the user's own notes, ready to paste into the team chat, with an optional short follow-up thread for extra detail. Use when the user asks for "standup", "my check-in", "daily update", or to put together…
Skill Claude CodeCodex
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to…
Instructions file
Claude Code instructions for luanmorenommaciel/agentspec, covering agentspec development, project context, repository structure, development workflow and explore an enhancement idea.
Hook
Runs when a session starts, executing init-workspace.sh. From luanmorenommaciel/agentspec.
Skill Claude CodeCodex
Data engineering expertise for pipelines, schemas, data quality, SQL, lakehouse, and streaming. Use PROACTIVELY when the user discusses data pipelines, ETL/ELT, schema design, dimensional modeling, data quality checks, SQL optimization, dbt models, Spark jobs, Airflow DAGs, streaming pipelines, lakehouse architecture…
Plugin Claude Code
Spec-Driven Development framework for Data Engineering — 58 agents, 24 KB domains, 5-phase SDD workflow, 31 commands.
luanmorenommaciel/uc-transact-co
MCP server Claude CodeCodexCursor +2
MCP server "transactco-cfo" as configured in luanmorenommaciel/uc-transact-co. Runs locally from the python Python package.
luanmorenommaciel/uc-transact-co
Instructions file CodexOpenCode
AGENTS.md instructions for luanmorenommaciel/uc-transact-co, covering transactco — agent instructions, ground rules (all agents, all engines), agents, architect — judgment, no hands and developer — execution, bounded hands.
luanmorenommaciel/uc-transact-co
Instructions file
Claude Code instructions for luanmorenommaciel/uc-transact-co: Follow @AGENTS.md — the ground rules and agent role definitions for this repository live there, in one place, for every engine.
luanmorenommaciel/uc-transact-co
Skill Claude CodeCodex
Regenerate the structural skeleton of a harness — agent role stubs, KB layout, and per-stack rule files — for a repository's stack, in seconds. Use when a harness structure must be (re)created from artifacts on disk, after the roles and contract are already understood and never before. Produces structure only: every…
luanmorenommaciel/uc-transact-co
Skill Claude CodeCodex
Turn an ambiguous question about an unfamiliar or brownfield system into a bounded, read-only, evidence-backed investigation with a confirmed investigation contract, deliberate context manifest, claim ledger, ontology, owned open questions, and reviewable technical brief. Use when asked to investigate a repository…
luanmorenommaciel/uc-transact-co
Skill Claude CodeCodex
Turn one reasonable-looking plan item into a single atomic Task-Spec that states its goal, the behaviour a named human signs, and the machine-runnable proof that answers "am I done?" without asking. Use when a backlog item, plan row, or ticket permits more than one defensible implementation; before handing work to an…
Plugin Claude Code
Plugin marketplace listing 1 plugin: brief-spec.
Plugin Claude Code
Type-aware, evidence-backed reading and delivery for AI coding agents.
Instructions file CodexOpenCode
Instructions for luanmorenommaciel/brief-spec: Before any task, read OPERATING.md. Do not invent a second loop. Do not skip the HMAC seal. Do not put family hops in docs/.
Instructions file
Instructions for luanmorenommaciel/brief-spec, a project described as: Type-aware, evidence-backed delivery contract for AI coding harnesses. Different agents in. One predictable human handoff out.
Hook
Runs when a session starts, running an inline shell check. From luanmorenommaciel/brief-spec.
Hook
Runs when you submit a prompt, before the agent sees it, running an inline shell check. From luanmorenommaciel/brief-spec.
Hook
Runs after a tool call finishes, running an inline shell check. From luanmorenommaciel/brief-spec.