@ai-outfitter/outfitter 0.3.0 → 0.4.0

package/requirements/OFTR-003-profiles.md

@@ -12,7 +12,7 @@ Outfitter resolves profile definitions across settings scopes, explicit sources,
 1. A profile MUST be represented by a folder with a required `profile.yml` file.
 2. Outfitter MUST provide a JSON Schema for `profile.yml`.
 3. Outfitter MUST validate every loaded `profile.yml` file against the profile JSON Schema.
-4. A profile folder MAY contain conventional resource folders such as `skills`, `prompts`, and `extensions`.
+4. A profile folder MAY contain conventional resource folders such as `skills`, `prompts`, `extensions`, and `deepwork/jobs`.
 5. A profile folder MAY contain `cli_specific/<cli-name>/` folders for agent-specific resources and overrides.
 
 ### OFTR-003.2: Profile Identity
@@ -37,11 +37,11 @@ Outfitter resolves profile definitions across settings scopes, explicit sources,
 4. Outfitter MUST detect inheritance cycles and report them as validation errors.
 5. Outfitter MUST preserve inherited profile order when building the profile stack.
 
-### OFTR-003.5: Implicit Default Profile
+### OFTR-003.5: Default Profile Selection
 
-1. The default profile from user settings MUST be included as an implicit bottom profile when running any explicit profile.
-2. Profiles inherited by the implicit default profile MUST be included recursively below the default profile according to the inheritance rules.
-3. Outfitter MUST avoid duplicating a profile in the resolved stack when the same profile appears explicitly and implicitly.
+1. Outfitter MUST use the configured `default_profile` only when no explicit profile is selected.
+2. When an explicit profile is selected, Outfitter MUST resolve only that profile and its declared `inherits` chain.
+3. Outfitter MUST NOT include the configured `default_profile` as an implicit base layer for an explicit profile.
 
 ### OFTR-003.6: Profile Merging
 
@@ -49,3 +49,11 @@ Outfitter resolves profile definitions across settings scopes, explicit sources,
 2. YAML object values SHOULD be merged with `defu` or an equivalent controlled deep-merge utility.
 3. Array merge behavior MUST be documented per profile key before that key is treated as stable.
 4. CLI-specific profile content MUST take precedence over generic controls when both generate the same agent-specific artifact.
+5. Outfitter MUST compose `append_system_prompt` values from multiple resolved profile layers into repeated agent append-prompt inputs without requiring profiles to use raw CLI `args` for prompt composition.
+
+### OFTR-003.7: Template Profiles
+
+1. A profile MAY set top-level `template: true` to indicate it is intended for inheritance by runnable profiles rather than direct launch.
+2. Outfitter MUST allow template profiles to contribute controls through `inherits` without marking the inheriting profile as a template.
+3. Outfitter MUST reject direct launches of template profiles, including launches selected through `default_profile`.
+4. `outfitter profile list` SHOULD hide template profiles by default and MUST expose them when the user explicitly requests all profiles.

package/requirements/OFTR-004-sync-and-setup.md

@@ -14,13 +14,23 @@ Outfitter provides setup and maintenance commands that create initial configurat
 4. The `setup` command MUST validate discovered settings files.
 5. The `setup` command MUST run sync behavior for URI-based profile sources.
 6. The `setup` command SHOULD avoid overwriting existing user files unless a future explicit force option authorizes replacement.
-7. When provided a setup source URI, the `setup` command MUST use that source repository's Outfitter `settings.yml` and profiles as the initial user setup starting point.
+7. When provided a setup source URI, the `setup` command MUST use that source repository's Outfitter `settings.yml` and profiles as the initial setup starting point for the selected import target.
 8. The interactive `setup` command MUST require interactive TTY streams on both stdin and stdout before prompting.
 9. The interactive `setup` command MUST synchronize remote profile sources before any setup profile choice prompt.
 10. Initial interactive first-run setup MUST NOT ask a separate default-profile choice before welcome onboarding; the welcome role selection determines the generated local default profile.
 11. When the interactive `setup` command presents setup profile choices outside the initial welcome handoff, it MUST present discovered profile IDs as default-profile choices and preserve available display labels in the prompt choices.
 12. When the interactive `setup` command presents setup profile choices outside the initial welcome handoff, it MUST validate the selected default profile ID before writing it to `settings.yml`.
 13. After the interactive `setup` command writes a selected default profile, any newly-created fallback default profile file MUST correspond to the final selected default profile.
+14. When interactive `setup <source>` presents setup profile choices, it MUST limit those choices to profiles from the passed setup source and MUST NOT include default profile sources from pre-existing effective settings.
+15. When interactive `setup <source>` presents setup profile choices and the setup source declares an explicit `default_profile` that exists among those source choices, it MUST make that profile the prompt default and first displayed choice; pre-existing user defaults MUST NOT override that source default for the setup-source prompt.
+16. Interactive `setup <source>` MUST NOT present a default-profile choice before the setup-source welcome/import explanation.
+17. Interactive `setup <source>` MUST explain which setup source is being imported and MUST let the user choose whether to install profiles into user home or the current project before writing setup-source profiles/settings.
+18. Interactive `setup <source>` MUST present exactly one setup-source profile/default choice after the import target choice when setup-source profiles are available.
+19. When the interactive setup-source import target is user home, setup MUST copy missing source profiles into `~/.outfitter/profiles`, write the selected default profile to `~/.outfitter/settings.yml`, and preserve non-overwrite copy behavior.
+20. When the interactive setup-source import target is the current project, setup MUST copy missing source profiles into `<project>/.outfitter/profiles`, write the selected default profile to `<project>/.outfitter/settings.yml`, ensure that project settings expose `./profiles`, and preserve any existing user default profile.
+21. After interactive `setup <source>` imports the selected default profile, setup MUST offer to start Outfitter with that selected profile.
+22. When the user declines the post-import start offer, setup MUST exit without launching and show both `outfitter` for starting the configured default profile and `outfitter --profile <selected-profile>` for starting it explicitly.
+23. Non-interactive `setup <source>` completion MUST NOT launch Outfitter and MUST show the same default and explicit start command guidance.
 
 ### OFTR-004.2: Sync Command
 

package/requirements/OFTR-006-agent-adapters.md

@@ -37,6 +37,8 @@ Pi is the default and primary supported adapter; Claude Code is also supported t
 9. The pi adapter SHOULD support pi model, provider, and thinking controls where native pi flags exist.
 10. The pi adapter MUST merge `.mcp.json` files from contributing `cli_specific/pi/` profile folders into the composite profile, adding unique array entries by identity while keeping the last entry for duplicate identities.
 11. The pi adapter MUST make native Pi `models.json` available inside the composite profile so custom providers and model definitions are visible before Pi resolves `--provider` and `--model` flags.
+12. The pi adapter MUST expose valid Agent Skills from contributing profile `skills/` folders as `--skill` arguments, and MAY also expose Pi-specific skills from `cli_specific/pi/skills/`.
+13. The pi adapter MUST expose DeepWork jobs from contributing profile `deepwork/jobs/` folders through `DEEPWORK_ADDITIONAL_JOBS_FOLDERS`, and MAY also expose Pi-specific jobs from `cli_specific/pi/deepwork/jobs/`.
 
 ### OFTR-006.4: Pi Startup Boundary
 

package/requirements/OFTR-009-release-publishing.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-Outfitter release publishing prepares package metadata from a GitHub release tag and publishes the `@ai-outfitter/outfitter` npm package through GitHub Actions.
+Outfitter release publishing prepares package metadata from Conventional Commit release PRs and GitHub release tags, then publishes the `@ai-outfitter/outfitter` npm package through GitHub Actions using npm trusted publishing / OIDC.
 
 ## Requirements
 
@@ -22,4 +22,13 @@ Outfitter release publishing prepares package metadata from a GitHub release tag
 3. The npm release workflow MUST synchronize package metadata from the GitHub release tag before publishing.
 4. The npm release workflow MUST run CI checks before publishing.
 5. The npm release workflow MUST build the package before publishing.
-6. The npm release workflow MUST publish the public `@ai-outfitter/outfitter` package to the npm registry using an npm token secret.
+6. The npm release workflow MUST request `id-token: write`, use the `npm-publish` GitHub environment, and publish the public `@ai-outfitter/outfitter` package to the npm registry with provenance through npm trusted publishing / OIDC rather than `NPM_TOKEN` or `NODE_AUTH_TOKEN`.
+
+### OFTR-009.3: Conventional Commit Release Automation
+
+1. The Release Please workflow MUST run on pushes to `main`.
+2. The Release Please workflow MUST use `googleapis/release-please-action@v4` with the upstream example-style token input from `secrets.RELEASE_PLEASE_TOKEN`.
+3. The Release Please workflow MUST use `release-type: node` for the root `@ai-outfitter/outfitter` npm package.
+4. The Release Please workflow MUST derive version bumps from Conventional Commits.
+5. The Release Please workflow MUST update npm package metadata and changelog through a release PR before publishing.
+6. The Release Please workflow MUST use GitHub repository write auth capable of triggering release PR CI and the release-published npm workflow, not the default `GITHUB_TOKEN`.

package/requirements/OFTR-010-onboarding-welcome.md

@@ -9,6 +9,7 @@ Outfitter welcome onboarding guides a new user through the minimum choices neede
 ### OFTR-010.1: Welcome Text
 
 1. Welcome text MUST be shown to the user explaining what Outfitter and Pi are.
+2. Welcome text MUST use Outfitter-branded ASCII/text.
 
 > Pi is a heavily customizable coding harness.
 > The next few questions will configure Outfitter to best suit your workflow.

package/src/schemas/profile.schema.json

@@ -9,6 +9,7 @@
       "pattern": "^[a-z0-9][a-z0-9._-]*[a-z0-9]$|^[a-z0-9]$"
     },
     "label": { "type": "string" },
+    "template": { "type": "boolean" },
     "inherits": {
       "type": "array",
       "items": {
@@ -43,7 +44,7 @@
         },
         "prompt_template": { "type": "string" },
         "system_prompt": { "type": "string" },
-        "append_system_prompt": { "type": "string" },
+        "append_system_prompt": { "$ref": "#/$defs/appendSystemPrompt" },
         "environment": {
           "type": "object",
           "additionalProperties": { "type": "string" }
@@ -69,7 +70,7 @@
             },
             "prompt_template": { "type": "string" },
             "system_prompt": { "type": "string" },
-            "append_system_prompt": { "type": "string" },
+            "append_system_prompt": { "$ref": "#/$defs/appendSystemPrompt" },
             "allow_external_deepwork_jobs": { "type": "boolean" },
             "environment": {
               "type": "object",
@@ -99,7 +100,7 @@
             },
             "prompt_template": { "type": "string" },
             "system_prompt": { "type": "string" },
-            "append_system_prompt": { "type": "string" },
+            "append_system_prompt": { "$ref": "#/$defs/appendSystemPrompt" },
             "environment": {
               "type": "object",
               "additionalProperties": { "type": "string" }
@@ -111,5 +112,16 @@
       "additionalProperties": true
     }
   },
-  "additionalProperties": true
+  "additionalProperties": true,
+  "$defs": {
+    "appendSystemPrompt": {
+      "oneOf": [
+        { "type": "string" },
+        {
+          "type": "array",
+          "items": { "type": "string" }
+        }
+      ]
+    }
+  }
 }