Revise skill development process documentation

Updated the process documentation for skill development, including changes to function names and validation steps.

Author: ericelliott

ai/skills/aidd-upskill/references/process.md

@@ -20,50 +20,54 @@ createSkill(userRequest) {
 ## Steps
 
 **gatherRequirements(userRequest)**
-1. discoverRelatedSkills — search `$projectRoot/ai/` and `$projectRoot/aidd-custom/` for SKILL.md, `.mdc`, `.md` files; read frontmatter descriptions; identify overlap or complementary skills
+1. discoverRelatedSkills — search the project for SKILL.md, `.mdc`, `.md` files; read frontmatter descriptions; identify overlap or complementary skills
 2. researchBestPractices — use web search to find best practices for the domain; summarize findings
 3. Infer requirements from the above context. Do not ask clarifying questions or block on user input. Use a judge to evaluate completeness: yes → proceed; no → state gaps as explicit assumptions and proceed.
 
-Infer answers to these questions from context rather than asking the user:
+Infer answers to these questions from context:
 - What problem does this skill solve?
 - What are its inputs and outputs?
 - Any technical constraints or requirements?
 - Should it `alwaysApply`? (recommend yes only if it applies to nearly every task)
 
 **nameSkill(topic)**
-- Use verb or role-based noun form (e.g., `aidd-format-code`, `aidd-upskill`)
-- Validate against `SkillName` type constraints
+- Use verb or role-based noun form (e.g., `format-code`, `upskill`)
 
 **buildPlan() => SkillPlan**
-Produce a `SkillPlan` struct (see `references/types.md`).
+Produce a `SkillPlan`
 
 **presentPlan(plan: SkillPlan)**
 Show the full plan, then run a self-validating quality gate — do not await user approval:
-1. Run `/aidd-review` on the plan
-2. Issues found => run `/aidd-fix` loop until all issues are resolved
-3. Proceed to `draftSkillMd`
+
+While important issues remain {
+  reviewPlan |> fix
+}
 
 **draftSkillMd(plan: SkillPlan)**
 - Write frontmatter: `name` + `description` required; add `metadata.alwaysApply` if needed
 - Write body with all `RequiredSections`
 - If body will exceed the line threshold (run `validate-skill` to check), extract content to `references/` and use `import $referenceFile`
 
 **writeSkill(skillMd)**
-- Write to `$projectRoot/aidd-custom/skills/${skillName}/SKILL.md`
-- Create `scripts/`, `references/`, or `assets/` directories only if planned
+- Write to `$skillHome/${skillName}/SKILL.md`
+- Create `scripts/`, `references/`, or `assets/` directories as required
 
 **writeReadme(skillMd)**
 - Write `README.md` in the skill directory
 - Include: what the skill is, why it is useful, command reference with usage examples
 - Exclude: implementation details, process narratives, pipeline descriptions
+- Avoid tables
+
 
 **validate**
 ```bash
-ai/skills/aidd-upskill/scripts/validate-skill ./path-to-skill-directory
+/validate-skill ./path-to-skill-directory
 # If skills-ref is available:
 skills-ref validate ./path-to-skill-directory
 ```
 
+If CLI access is unavailable, carefully emulate the validation process.
+
 **reportMetrics**
 Report `SizeMetrics` and any threshold warnings to the user.