technobureau
5 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
technobureauai-init
Bootstrap or refresh an evidence-grounded, stakeholder-readable documentation set for a new or existing repository. Use when asked to initialize AI context, create or refresh README.md or AGENTS.md, map repository structure, record architecture decisions, or establish baseline project documentation. Routes PRD, security, tests, design, and code-quality work to dedicated skills.
- instalaciones
- 1
- GitHub Stars
- 0
- Actualizado
- 20 oct
technobureaucode-quality
Improve maintainability and secure engineering quality by removing verified dead code and applying modular, documented, testable practices, API compatibility rules, dependency hygiene, and observability standards. Use for explicit cleanup, refactoring, code review, or code-standard tasks; not as a side effect of documentation.
- instalaciones
- 1
- GitHub Stars
- 0
- Actualizado
- 20 oct
technobureauprd
Create or refine a concise, implementation-grounded Product Requirements Document with permanent G-, D-, FR-, and NFR-IDs, acceptance criteria, and enterprise traceability. Use when a repository PRD is requested, when requirements must be clarified or audited, or when ai-init is documenting a product repository.
- instalaciones
- 1
- GitHub Stars
- 0
- Actualizado
- 20 oct
technobureausecurity
Create or refine an evidence-based, modular enterprise security profile, including applicable threat modeling, supply-chain, cryptographic agility/PQC, FIPS, OpenSCAP/SCAP, CIS, NIST, ISO/IEC 27001, OWASP, and AI/LLM controls. Use for repository security analysis, secure-design review, audit preparation, or posture documentation; implement hardening only when explicitly requested.
- instalaciones
- 1
- GitHub Stars
- 0
- Actualizado
- 20 oct
technobureautests
Add, improve, review, or document repository tests using the project's existing frameworks and verified commands, with enterprise coverage of functional, security, accessibility, performance, and resilience risks. Use only when test work, test strategy, test evidence, or docs/tests.md is requested; testing documentation is not part of ai-init's default output.
- instalaciones
- 1
- GitHub Stars
- 0
- Actualizado
- 20 oct