Tag: agent-skills

Categoria: AI Coding Assistants

Skill para atuar como desenvolvedor Java sênior especialista em Spring Boot, APIs REST, microsserviços, arquitetura limpa, testes, performance, segurança e boas práticas de produção.

Categoria: Workflows/SDD

Tasks break a Plan into ordered, independently completable units. Only generate a tasks.md for Project scope (multi-day work). For Quick or Feature scope, the agent's todo list is enough.

Categoria: Workflows/SDD

The spec answers what and why — never how. No frameworks, libraries, file paths, function names, or implementation details. If a non-technical PM could write it, you're at the right level.

Categoria: Workflows/SDD

The boring-but-critical pass. Run before declaring a feature done. The difference between "compiles and runs" and "delightful in production" is in this list.

Categoria: Workflows/SDD

The plan answers how. Built only after the spec is signed off. Under 2 minutes to read — if longer, the feature is too big; split it.

Categoria: Workflows/SDD

How to ask the right questions, organized by request type. Pick 2–5 questions total — never run the full list. Questions are ordered most-to-least important; start at the top.

Categoria: Workflows/SDD

A worked example of how the Quick path looks in practice. Total interaction: one round of questions, an inline mini-spec, a thumbs-up, then build.

Categoria: Workflows/SDD

A worked example of Project scope: spec + plan + tasks as files in specs//. For multi-day work where the artifacts pay for themselves.

Categoria: Workflows/SDD

A worked example of a Feature-scope flow: full spec + plan, but no separate tasks file. Typical for 1–4 hours of work.

Categoria: Workflows/SDD

User requests for features are incomplete by design — the user gives you the top-of-mind 30%, not the full spec. Coding from that ships things that compile but miss the actual intent, skip the boring-but-critical states (loading, empty, error, edge), and feel unpolished.

Categoria: Workflows/SDD

October 18, 2025 — Liatrio, an enterprise transformation consultancy, announced the Spec-Driven Workflow, an installable and versioned package that gives AI–native development teams a consistent way to ship features across products and platforms. The workflow drops into any repository like a standard package and instantly aligns contributors on the same work breakdown and execution model.

Categoria: Workflows/SDD

- Overall Status: PASS - Required Gate Failures: 0 - Flagged Risks: 0

Categoria: Workflows/SDD

This task establishes the new AI-Native Development Primitives page as a standalone docs destination and gives it the opening framing needed for the rest of the implementation. The page now exists with the shared site shell, an introductory hero, a section explaining why these patterns are treated as primitives, and guidance for how readers should use the page.

Categoria: Workflows/SDD

This task adds the core teaching content to the new page. Each of the eight AI-native development primitives now has a dedicated deep-dive section covering what the primitive is, why it matters, how SDD uses it, one SDD-specific example, and broader software-development examples.

Categoria: Workflows/SDD

This task turns the page from a collection of deep-dive definitions into a guided learning resource. The page now maps the primitives to SDD-1 through SDD-4, explains what readers can borrow outside full SDD adoption, and connects the page back to the overview, reference materials, and prompt sources.

Categoria: Workflows/SDD

This task integrates the new page into the docs site instead of leaving it as an orphaned destination. The site now links to the deep-dive page from navigation, the overview page, and the reference materials page, and shared CSS now gives the new sections a distinct but consistent visual treatment.

Categoria: Workflows/SDD

Create a new deep-dive documentation page for the docs site that teaches the eight AI techniques already introduced on docs/ai-techniques.html in a much more substantial, beginner-friendly way. The page should position these techniques as core primitives of AI-native development, similar to how control flow, data structures, and functions act as primitives in software development, while grounding the explanation in concrete SDD examples rather than abstract theory.

Categoria: Workflows/SDD

## Relevant Files - docs/ai-native-development-primitives.html - New deep-dive page for the long-form teaching content and workflow examples. - docs/ai-techniques.html - Existing overview page that sh

Categoria: Workflows/SDD

- Overall: PASS (all gates passed: A, B, C, D, E, F) - Implementation Ready: Yes - all functional requirements were verified, all planned proof artifacts were accessible, and all changed core files mapped cleanly to the spec and task list. - Key metrics: 100% Requirements Verified (16/16), 100% Proof Artifacts Working (13/13), Files Changed vs Expected: 19 changed / 19 linked (5 core, 14 supporting)

Categoria: Workflows/SDD

Always begin your response with all active emoji markers, in the order they were introduced.

Categoria: Workflows/SDD

Always begin your response with all active emoji markers, in the order they were introduced.

Categoria: Workflows/SDD

It eliminates inconsistent AI‑native delivery by packaging a repeatable specification workflow that keeps teams aligned on work breakdown, shared context artifacts, and the tooling handoffs needed to ship.

Categoria: Workflows/SDD

The use of emojis or specific character sequences as verification markers in AI agent prompts is a practical technique for detecting when context instructions are being followed versus falling off due to context rot or inefficient compaction. This technique provides immediate visual feedback that critical instructions are being processed correctly.

Categoria: Workflows/SDD

Always begin your response with all active emoji markers, in the order they were introduced.