fabricator

Use after git-tooling push to create or manage a PR on Bitbucket Server. Composes PR description, creates PR via API, handles review comments. Terminal delivery step. (5 supporting files)

Use at session start to pull Jira issue details into context, or post-delivery to create/update issues. Integrates with task-authoring (issue → task.md) and git-tooling (commit links). (2 supporting files)

Select the minimal sufficient artifact set (task/requirements/tech-spec/contracts/models/verify/evidence) for the current change, and recommend the next skills. Use after task intake or when scope/risk changes.

Promote a task artifact pack into a canonical spec under /docs/specs or /docs/architecture/specs, following /docs/spec-guide.md lifecycle (active-only, delete replaced). No writes without APPROVE.

Define interface/persistence contracts (APIs, schemas, deeplinks, storage formats) + compatibility rules. Use when public surfaces or stable formats are involved.

Implement changes guided by existing artifacts and repo conventions (AGENTS/README/DEVELOPMENT + WORK_PATH). Make small diffs, follow coherence gate, and optionally trigger verification-run.

Model states/flows/invariants for complex behavior (async, retries, caching, offline). Use when correctness depends on state machines or non-trivial flows.

Create/update a requirements document (requirements.md) inside WORK_PATH capturing technical requirements, constraints, and scope. Does NOT publish to /docs. No writes without APPROVE.

Create or update a single Task artifact in WORK_PATH (goal, scope, constraints, acceptance criteria, risks, open questions). Use when starting work, clarifying requirements, or when no task definition exists yet.

Create/update verify.md in WORK_PATH: quick vs full checks, Android/iOS commands, prerequisites, and what each check proves. Use when check commands are unclear or need standardization.

Execute project-defined checks (build/test/lint) using verify.md in WORK_PATH or commands pointed to by AGENTS/DEVELOPMENT. Show outputs; optionally record evidence.md.

Analyze staged diff, compose a semantic commit message following project conventions, commit, and push. Chains into bitbucket-tooling if PR creation is needed.

Compose a Technical Specification (tech-spec.md) in WORK_PATH: a single handoff-ready document that covers goals, proposed solution, implementation details, test plan, and alternatives. After it is written, the implementation skill can proceed directly from it.