@multileaf/ai-workflow 0.1.3 → 0.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +29 -1
- package/README.md +54 -46
- package/dist/adapter.js +13 -11
- package/dist/generator.js +18 -6
- package/dist/profile.d.ts +19 -0
- package/dist/profile.js +145 -10
- package/dist/quality-gates.d.ts +1 -1
- package/dist/quality-gates.js +19 -10
- package/dist/recommendations.d.ts +1 -0
- package/dist/recommendations.js +107 -12
- package/dist/selection.js +38 -2
- package/dist/workflow.js +83 -16
- package/docs/ai-init-workflow-spec.md +47 -0
- package/docs/backlog.md +1 -0
- package/docs/product-requirements.md +1 -0
- package/package.json +1 -1
- package/resources/agents/nestjs-engineer.md +3 -0
- package/resources/agents/prisma-engineer.md +3 -0
- package/resources/package.yaml +64 -4
- package/resources/rules/data-access-policy.md +7 -0
- package/resources/skills/brainstorming.md +1 -0
- package/resources/skills/code-review.md +1 -0
- package/resources/skills/implementation-planning.md +1 -0
- package/resources/skills/nestjs-development.md +8 -0
- package/resources/skills/prisma-data-access.md +8 -0
- package/resources/skills/project-init.md +1 -2
- package/resources/skills/requirements-specification.md +1 -0
- package/resources/skills/tdd-development.md +1 -0
- package/resources/skills/technical-design.md +1 -0
- package/resources/skills/verification.md +1 -0
- package/resources/skills/vite-frontend.md +8 -0
|
@@ -7,3 +7,4 @@ description: Convert a product idea into testable, traceable requirements.
|
|
|
7
7
|
|
|
8
8
|
Give each requirement a stable identifier. Define observable behavior, acceptance criteria, constraints, and unresolved questions. Link requirements to their source brainstorm and distinguish confirmed facts from assumptions. Do not approve ambiguous critical requirements.
|
|
9
9
|
|
|
10
|
+
After requirements are confirmed, use `technical-design` when the change affects architecture or has consequential design choices; otherwise hand off to `implementation-planning`.
|
|
@@ -7,3 +7,4 @@ description: Implement repository changes through test-first development.
|
|
|
7
7
|
|
|
8
8
|
Follow Red, Green, Refactor, Verify. Write a failing behavioral test first, implement the smallest change, refactor for clarity and design quality, then run the relevant quality gate. Never weaken a test to make an implementation pass.
|
|
9
9
|
|
|
10
|
+
After implementation tasks are green and refactored, hand off to `verification` with the changed requirements, test commands, and evidence.
|
|
@@ -7,3 +7,4 @@ description: Design modular technical solutions from approved requirements.
|
|
|
7
7
|
|
|
8
8
|
Map requirements to components, interfaces, data flows, and validation strategy. Compare meaningful alternatives and record decisions with rationale, risks, and consequences. Prefer small cohesive modules, explicit contracts, dependency inversion, and reversible changes.
|
|
9
9
|
|
|
10
|
+
Link each design and ADR to the affected requirements. Once decisions are recorded, hand off to `implementation-planning`.
|
|
@@ -7,3 +7,4 @@ description: Verify implementation against requirements and produce traceable ev
|
|
|
7
7
|
|
|
8
8
|
Check every acceptance criterion, quality gate, security requirement, and affected adapter. Report passed checks, missing evidence, failures, and residual risks. A task is not complete when required evidence is missing.
|
|
9
9
|
|
|
10
|
+
Create the verification report and validate it with `npx --yes --package=@multileaf/ai-workflow -- aiw gate verification`. Then hand off to `code-review` when installed; after review, update traceability and completion evidence.
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: vite-frontend
|
|
3
|
+
description: Build and verify Vite frontends using the repository's framework, module, and test conventions.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Vite Frontend
|
|
7
|
+
|
|
8
|
+
Inspect the Vite entry point, framework plugins, route/component structure, and workspace-local scripts before making changes. Follow the existing component, state, styling, accessibility, and API-client patterns. Keep frontend configuration scoped to the correct workspace. Add focused tests with the configured runner and verify the workspace's declared lint, typecheck, and build commands. Do not assume that a root-level command applies to every app in a monorepo.
|