pi-aia-asf 0.1.0 → 0.1.1
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 +7 -0
- package/package.json +1 -1
- package/skills/aia-asf/SKILL.md +13 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [0.1.1] - 2026-08-14
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- **The `aia-asf` skill was never loaded.** Its YAML frontmatter description contained an unquoted colon (`The flow is: classify the work...`); a colon followed by a space starts a mapping in YAML, so the frontmatter failed to parse and pi silently skipped the skill. The extension's `/asf` commands worked, but the workflow skill itself was unavailable. The description is now a YAML block scalar with no inline colon.
|
|
15
|
+
|
|
16
|
+
|
|
10
17
|
### Added
|
|
11
18
|
|
|
12
19
|
- Initial release of the Ai Applied Agentic Software Factory.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-aia-asf",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "Ai Applied Agentic Software Factory — codifies the full software development flow: intake, research, spec capture, adversarial analysis, planning with approval gates, test-first implementation, and release. Requires pi-vigilant, pi-smart-web-search, pi-smart-fetch, and pi-aia-browser.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
package/skills/aia-asf/SKILL.md
CHANGED
|
@@ -1,6 +1,18 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: aia-asf
|
|
3
|
-
description:
|
|
3
|
+
description: >-
|
|
4
|
+
Agentic Software Factory — run a complete, disciplined software development
|
|
5
|
+
cycle. Use when the user wants to start a NEW software project, add a
|
|
6
|
+
SIGNIFICANT FEATURE to an existing project, perform a MAJOR BUGFIX, or do an
|
|
7
|
+
ARCHITECTURAL REFACTOR. The flow classifies the work, asks questions until the
|
|
8
|
+
intent is clear, researches SOTA and existing packages, captures hard
|
|
9
|
+
specifications (via capture_spec, shared with pi-vigilant), runs adversarial
|
|
10
|
+
analysis, produces a PLAN.md and gets explicit user approval, then implements
|
|
11
|
+
test-first with strict codebase isolation and mandatory browser testing of any
|
|
12
|
+
web interfaces (pi-aia-browser). Do NOT activate for simple Q&A, one-line
|
|
13
|
+
fixes, casual conversation, content writing, or non-software tasks. When in
|
|
14
|
+
doubt about whether work qualifies as a project/feature/bugfix/refactor, ask
|
|
15
|
+
the user.
|
|
4
16
|
---
|
|
5
17
|
|
|
6
18
|
# AIA Agentic Software Factory (ASF)
|