feature
/feature
Discover-plan-implement-verify-record workflow for implementing a feature or a step of an implementation plan in a Swift/SwiftUI macOS app without architectural drift. Use when starting work on a new feature, a roadmap step, or a change that touches more than one module.
- Author
- davidelarocca ↗
- Repository
- swift-harness ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Discover-plan-implement-verify-record workflow for implementing a feature or a step of an implementation plan in a Swift/SwiftUI macOS app without architectural drift. Use when starting work on a new feature, a roadmap step, or a change that touches more than one module.
Original author description
Discover-plan-implement-verify-record workflow for implementing a feature or a step of an implementation plan in a Swift/SwiftUI macOS app without architectural drift. Use when starting work on a new feature, a roadmap step, or a change that touches more than one module.
How it works
- 0. Branch and checkpoint
- 1. Discover
- 2. Plan
- 3. Implement
- 4. Verify
- 5. Record
SKILL.md preview
--- name: feature description: Discover-plan-implement-verify-record workflow for implementing a feature or a step of an implementation plan in a Swift/SwiftUI macOS app without architectural drift. Use when starting work on a new feature, a roadmap step, or a change that touches more than one module. --- # Feature workflow Step-by-step plans keep each session focused. This workflow adds the checks between steps that keep the steps consistent with each other. ## 0. Branch and checkpoint - Work on a branch named after the feature or step. If on the main branch, create one first. - Start from a clean tree. If there are uncommitted changes that are not yours to commit, stop and ask. - With parallel agents or worktrees: several agents may analyze or review in parallel, but one agent integrates. Never let two agents edit the same files. ## 1. Discover Read only what the change needs: 1. `CLAUDE.md` is already loaded. Follow its links only where relevant. 2. The feature spec or step document the user points to. 3. `docs/COMPONENT_REGISTRY.md` if the change has any UI. 4. `docs/PRODUCT_MAP.md` if the change shows an entity somewhere, adds an entity, or adds something the user creates or organizes. 5. The ADRs that touch the modules involved. 6. The actual code of the modules involved, and the callers of anything you plan to change. Then state in a few lines: what exists already, what the docs say that the code contradicts (if anything), and what you will reuse. ## 2. Plan - Files to create and modify, grouped by module. - New dependencies between modules, if any, and why. - UI decisions per the `ui-change` skill (reuse, extend, create). - Product coherence, when the map applies: for each place an entity appears, how the user opens it, which related entities shown there are reachable, and which actions it offers. For a new entity: its destination, relations and action set. For a user-managed collection: create, rename, reorder, delete, undo. Anything left out is stated, not silent. - Risks, including anything in protected paths. - Tests to add or update, and how the result will be verified. For changes that cross modules or touch protected paths, present the plan and wait for approval. For small single-module changes, state the plan and proceed. ## 3. Implement - Smallest change that satisfies the step. No drive-by refactors; list them as follow-ups instead. - UI through the design system only. - Logic in models or services, with tests next to it. Pure logic (ordering rules, queues, parsing) gets unit tests with Swift Testing first. - Do not edit `project.pbxproj` by hand. ## 4. Verify - Run `scripts/verify.sh fast` (the Stop hook runs it too, but run it yourself before claiming done). - For UI changes: previews in every state, snapshots for shared components, and a look at the running app or a screenshot when the change is visual. - Report exactly what ran and what did not. "Not verified" is an acceptable answer; a false "passes" is not. ## 5. Record In the same change: - `docs/COMPONENT_REGISTRY.md` for any UI component added, extended or retired. - `docs/PRODUCT_MAP.md` for any entity, appearance, relation, action or collection added or changed, and for deliberate exceptions. - The feature or step document: mark what is done, note deviations from the plan and why. - `docs/ARCHITECTURE.md` if a module, dependency or data flow changed. - An ADR (via the `adr` skill) if you made a decision a future session could otherwise reopen. Finish with a short summary: what changed, what was verified, follow-ups.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · davidelarocca/swift-harness | 90 | MIT |
| A7-studio/jobmigo | 100 | MIT |
| crbnos/carbon | 100 | AGPL-3.0 |
| arxdsilva/ai-loops | 100 | MIT |
| jisuzzzz/haechi | 100 | MIT |
| pawangai/pawang-agents | 100 | MIT |
| andrewBezerra/concordia | 100 | MIT |
| cryndoc/polisade-orchestrator | 100 | Apache-2.0 |
| ChandraChaan/flutter-agent-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version b31f5906d692 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90audit
Read-only architecture, UI consistency and code health audit of a Swift/SwiftUI macOS project, producing a prioritized report and an incremental migration plan. Use when the user asks for an audit, a codebase review, or a starting point before refactoring. - 86swift
Swift开发专家助手。当用户需要进行Swift语言开发、iOS/macOS应用、SwiftUI、Vapor后端或Apple生态开发时调用。 - 100swift-app-scaffold
Use when starting a new iOS or macOS app, bootstrapping Package.swift, or scaffolding a modern SwiftUI architecture with Observation, SwiftData, NavigationStack, and Swift Testing. - 100macos-apps
Build professional native macOS apps in Swift with SwiftUI and AppKit. Full lifecycle - build, debug, test, optimize, ship. CLI-only, no Xcode. Use when asked to: create macOS apps, build Swift apps, develop SwiftUI interfaces, fix macOS app issues, add macOS app features, or… - 100swift-swiftui
Swift 6 and SwiftUI code rules for macOS apps, including concurrency, state, SwiftData, AppKit bridges, and fixes for common compiler errors. Use when writing, reviewing, or debugging Swift code in a Mac app, or on concurrency, Sendable, or "not in scope" errors. - 100swift-swiftui
Swift 6 and SwiftUI code rules for macOS apps, including concurrency, state, SwiftData, AppKit bridges, and fixes for common compiler errors. Use when writing, reviewing, or debugging Swift code in a Mac app, or on concurrency, Sendable, or "not in scope" errors.