Guides structured dialogue to write and approve technical specification documents.
npx skills add https://github.com/oporpino/commons --skill br4zz4-spec-oporpino
Please help me install this Agent Skill. Skill: br4zz4:spec Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Aspec Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-spec-oporpino
.project/docs/specs/ with Portuguese body, English frontmatter, status tracking, and commits them to git. - Optional visual companion: Starts a local browser server to present layout or architecture options as clickable HTML mockups when decisions are visual. - Use Case: A developer wants to add a new feature. The skill walks them through understanding the problem, comparing implementation approaches, writing an approved spec, and handing off to the planning skill. ## Quick Start Ask the assistant to plan and document a change before implementing it, then answer its questions one at a time until the spec is written and approved.High-intent search queries and answers about installing and using this skill.
Invoke the spec skill and answer its questions one at a time. It explores your project docs and git history, proposes 2-3 approaches with trade-offs, then writes a timestamped Markdown spec to .project/docs/specs/ and commits it after your approval.
The workflow is: explore context, link an Asana task, dialogue to understand the problem, propose approaches, write and self-review the spec, get explicit approval, then hand off to the plan skill. No code is written until the spec is approved.
It searches for related Asana tasks using asana_search_tasks based on the product inferred from your working directory. It only creates a new task after you explicitly confirm, and never asks you for a task ID.
Use it only for genuinely visual questions like UI layouts, wireframes, or architecture diagrams. It starts a local server rendering HTML option fragments in the browser. Conceptual or trade-off questions stay in the terminal.
It never writes code, creates branches, or implements anything. Over-scoped requests spanning multiple subsystems are flagged for decomposition first, and specs must be written fresh rather than overwriting previous ones.
sgpropertyanalyticsEnforce architecture guardrails and produce a findings report before implementation tasks.
liuzeming-yuxiTransform an approved spec into an executable plan for Claude Code.
Adelie-SquadGenerate Job Stories, User Stories, and Gherkin acceptance criteria from product briefs.
KbediakoConducts on-demand reviews of tasks and specifications without running pipelines.